Re: [boost] scoped_ptr rationale

From: Peter Dimov (pdimov_at_[hidden])
Date: 2002-09-21 10:23:34

From: "Howard Hinnant" <hinnant_at_[hidden]>
> I can see several useful smart pointers here (though I do not yet know
> their names):
>
> 1.  no copy semantics, no move semantics.
> scoped_ptr without a reset, or as you note const auto_ptr could satisfy
> this.
>
> 2.  move semantics, no copy semantics.
> move_ptr.
>
> 3.  copy semantics, no move semantics.
> shared_ptr, and/or a deep-copy "clone ptr" could fill this role.
>
> 4.  copy semantics, move semantics.
> Same as #3.  Once you have copy semantics, move semantics is just an
> optimization.  It should not effect interface.

I think that you missed the "swap semantics" axis. reset() is on "swap", not
on "copy" or "move" as sp.reset(args) is a shorthand for
smart_ptr(args).swap(sp).