🚀 go-pugleaf

In article <472ujv$ns0@engnews1.eng.sun.com> clamage@Eng.Sun.COM (Steve Clamage) writes:

   >Right now, I think it makes sense disallowing them.

   The problem is actually a little more subtle. You also have to disallow
   passing the value of "this" out of a constructor or destructor, or 
   make the results of doing so undefined.

... which would invalidate the common idiom:

	class A {
		Destroy();
		Copy(const A&);
	public:
		~A() { Destroy(); }
		A(const A& a) { Copy(a); }
		operator=(const A& a) { Destroy(); Copy(a); }
	}

... and hence is probably unacceptable.

Greg.
--
Gregory Bond <gnb@bby.com.au> Burdett Buckeridge & Young Ltd Melbourne Australia
``Efforts to maintain the "purity" of a language only succeed in establishing an
  elite class of people who know the shibboleths.  Ordinary folks know better, 
  even if they don't know what "shibboleth" means.'' - Larry Wall

[ comp.std.c++ is moderated.  Submission address: std-c++@ncar.ucar.edu.
  Contact address: std-c++-request@ncar.ucar.edu.  The moderation policy
  is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]