Peter Dimov wrote: > > intrusive_ptr will be "official" (read: I finally wrote something resembling > a documentation) in the upcoming 1.30. But that's not my point. My point is > that you need an intrusive smart pointer. Of course shared_ptr cannot offer
I know I needed an intrusive smart pointer, the question was how to get it. For Loki, it took me some time to figure out some details on how to write the correct policy and it then worked fine. For boost, I only found the solution for shared_ptr and was surprised to see the object growing that much. > this with its non-intrusive design. It never attempted to. The optional > intrusive counting "feature" (that's been removed) was offered only as a > potential solution to the "shared from this" problem. I understand. Well, I think I should then try to add intrusive_ptr to my benchmark and see how it performs :) Regards, Daniel -- Daniel Frey aixigo AG - financial training, research and technology Schloß-Rahe-Straße 15, 52072 Aachen, Germany fon: +49 (0)241 936737-42, fax: +49 (0)241 936737-99 eMail: [EMAIL PROTECTED], web: http://www.aixigo.de _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost