Re: [boost] Smart Pointer new/Forwarding Problem Solved (by Force)

From: David Abrahams (dave_at_[hidden])
Date: 2006-03-29 15:46:21

"Peter Dimov" <pdimov_at_[hidden]> writes:

> David Abrahams wrote:
>> David Abrahams <dave_at_[hidden]> writes:
>> 
>>> Unfortunately for this particular facility, the converting
>>> constructor is explicit, so you can't do
>>> 
>>>    f(new_<T>(a, b, c))
>>> 
>>> if f takes a shared_ptr<T>.
>> 
>> I just realized we could probably fix this by removing an "explicit"
>> from the ctor that accepts an rvalue auto_ptr.  What about that,
>> Peter?  This seems like a poster child for rvalue distinction!
>
> Done.

Cool!  Just in case it wasn't obvious: we should do this across all
the smart pointers.  It looks like scoped_ptr could use the same
treatment, for example.

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