Re: [boost] [shared_ptr] Best Practices - new_shared_ptr

From: David Abrahams (dave_at_[hidden])
Date: 2006-03-24 15:56:57

Larry Evans <cppljevans_at_[hidden]> writes:

> On 03/24/2006 11:00 AM, David Abrahams wrote:
> [snip]
>> Yes, the library ought to contain something like that, as I have been
>> saying for years.  Probably it should be spelled something like:
>>      new_<shared_ptr<T> >(a, b, c, ...)
>>      new_<auto_ptr<T> >(a, b, c, ...)
>> Unfortunately, really making these functions work correctly for more
>> than about 5 or 6 arguments is currently not feasible because of
>> what's known as "the forwarding problem" (google it).
>> Boost Consulting is working on a project where we'll need this
>> functionality, so I hacked up the enclosed.  I'm going to generalize
>> it (and hopefully, optimize compilation speed) a bit and try to get it
>> into Boost.  In the meantime, enjoy.
>
> I tried to post the following but got an error.  I'm trying again,
> but I've also mailed directly to David in case I'm unsuccessful.
> <--------------- cut here -------------------

<snip>

> Of course I see that that would still require all the boost_pp
> forwarding magic in David's new_.hpp, but it would be nice if
> the new_ forwarding magic and that in auto_overhead could be
> merged somehow increase reuse.

That's what I meant when I wrote that I was going to generalize the
code.

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com