Re: Visual C++ 6.0 & MFC memory leaks

Alexander Nickolov wrote:


Um, those two are different beasts:
- std::auto_ptr guarantees exclusive ownership
- boost::shared_prt allows shared ownership

I'd say that there are different applications to both of them. Whenever I
want to transfer exclusive ownership, I use std::auto_ptr, so it is really
clear that the receiver can do whatever they want with the object and that
they are responsible for deleting it. If they decide to share it with other
parts of the code, that's easy, too, you have a constructor for shared_ptr
that takes an auto_ptr.

Anyway: the point about resource leaks (not just memory leaks!) is that
smart pointers or similar classes that enforce(!) certain ownership
semantics are an invaluable help. IOW the same principles that guide the
use of smart pointers are also applicable to e.g. filedescriptors or
handles. If you want, take a look at[1] where I hacked together a generic
resource holder with auto_ptr-like semantics. I'd sure like to know what
you think about this.

Uli

[1]: http://lists.boost.org/Archives/boost/2007/05/122359.php

--
With sufficient hate, Reff Jelf flies just fine. However, this is not
necessarily a good idea. It is hard to be sure where he is going to
land, and it could be dangerous sitting under him as he flies overhead.
(inconcisely paraphrasing RFC 1925)