29 Mar
2006
29 Mar
'06
8:46 p.m.
"Peter Dimov" <pdimov@mmltd.net> writes:
David Abrahams wrote:
David Abrahams <dave@boost-consulting.com> 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