🚀 go-pugleaf

Someone writes:
   >Actually, it occurs to me that the following does work:
   >
   >    auto_ptr< T >       f() ;
   >    auto_ptr< T >       p1( f().release() ) ;
   >	auto_ptr< T >		p2 ;
   >	p2.reset( f().release() ) ;
   >
   >Somehow, it just doesn't seem natural, though. 

There is a case where it doesn't work.

The problem is that you are passing it as a standard pointer type.
What happens if you were to run out of stack after the call to release
and before the call to the constructor, or reset.  And an exception is
thrown.

If your program actualy catches that exception then a memory leak has
occured. ( A rare case I will admit).

There are probably more realistic examples is less mundane code.

It must be in an object at all times TO BE SAFE!
---
[ 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. ]