[boost] Re: Re: shifted_ptr<> w/ lock mechanism

From: Philippe A. Bouchard (philippeb_at_[hidden])
Date: 2003-01-30 08:37:53

> To be fair, a factor of two improvement cannot just be shrugged off. But
one
> point to keep in mind is that
>
> shared_ptr<X> px(new X);
>
> performs two allocations. We can optimize the count allocation until we're
> blue in the face but in a real project the whole expression will probably
> remain a bottleneck; so it's likely that X will acquire a class-specific
> operator new. And a X with a class-specific new can no longer be used with
> shifted_ptr.

shifted_ptr is only a different alternative.  This depends on what the user
(or project manager) wish to use.

Philippe A. Bouchard