From: Ed Brey (brey_at_[hidden])
Date: 2002-07-16 17:08:29
In the 1.28.0 distribution, intrusive_ptr includes a non-explicit constructor and an assignment operator that take T*. This differs from shared_ptr, which provides neither. This is at best inconsistent and at worst dangerous. The danger is the same one that motivates shared_ptr to not deal implicitly in raw pointers; e.g. a function taking an intrusive_ptr can have an unmanaged pointer passed to where it can be unknowingly taken over by the intrusive_ptr.
Is there something unique about intrusive_ptr that makes it appropriate to differ from shared_ptr?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk