Re: scoped_ptr versus auto_ptr

From:

=?ISO-8859-1?Q?Daniel_Kr=FCgler?= <daniel.kruegler@googlemail.com>

Newsgroups:

comp.lang.c++.moderated

Date:

Tue, 7 Dec 2010 06:42:29 CST

Message-ID:

<idl1le$jso$1@news.eternal-september.org>

On 12/7/2010 10:01, Andrew wrote:
[..]

I would use std::unique_ptr but one of the compilers I have to use is
VS 2005 (aka vc8) which is ancient and not very conformant. It's
std::auto_ptr implementation is broken so I wouldn't trust its
implementation of std::unique_ptr even if it had one.

So I was wondering if there is a boost pointer that does the same job
as std::unique_ptr. There is a pointer by that name in
boost::interprocess (boost/interprocess/smart_ptr/unique_ptr.hpp) but
this takes more template arguments that just the type for the pointee.

Basically this implementation looks like a simulation of what
std::unique_ptr represents (I have not checked the details, though).

The second template parameter is also part of std::unique_ptr, the
so-called "deleter". The Standard component has the default type
default_delete. For non-arrays this function object type is more or less
defined as:

template <class T>
struct default_delete
{
     void operator()(T* ptr) const
     {
         BOOST_STATIC_ASSERT(sizeof(T) > 0);
         delete ptr;
     }
};

I am also puzzled by the interprocess namespace. It makes it looks
like it might have something to do with interprocess work.

It clearly isn't.

The documentation makes it look like it does the same job as
std::unique_ptr. The comments in the header say it is an adaptation
for Interprocess of Howard Hinnant's unique_ptr emulation code. Does
anyone know what that means please?

Howard Hinnant's original emulation code can be found here:

http://home.roadrunner.com/~hinnant/unique_ptr03.html

HTH & Greetings from Bremen,

Daniel Kr?gler

--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]