🚀 go-pugleaf

fjh@munta.cs.mu.OZ.AU (Fergus Henderson) writes:

I've compressed Fergus's example (for writing a constructor that is
safe from out-of-memory exceptions) a bit by putting the constructor inline.
The result goes like this.

class a {
public:
	auto_ptr<char> mBuffer1;
	auto_ptr<char> mBuffer2;
	a() {
	  mBuffer1 = new char[1000];
	  mBuffer2 = new char[1000];
	}
};

Looks good; no destructor needed.  But just a minute: auto_ptr<T>'s
destructor does

	delete T;

not

	delete [] T;

right?  This means this usage is incorrect, even though it so happens
that it will work in many implementations for objects without destructors.
Shouldn't there be a separate auto_array_ptr to handle pointers to arrays
correctly?

-- 
-- Joe Buck 	<jbuck@synopsys.com>	(not speaking for Synopsys, Inc)
Anagrams for "information superhighway":	Enormous hairy pig with fan
						A rough whimper of insanity
---
[ 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. ]