Re: shared_ptr and real world (explicitly loaded DLLs)

From:

=?iso-8859-1?q?Daniel_Kr=FCgler?= <daniel.kruegler@googlemail.com>

Newsgroups:

comp.lang.c++.moderated

Date:

Fri, 14 Sep 2007 18:00:20 CST

Message-ID:

<1189803775.247627.66700@y42g2000hsy.googlegroups.com>

On 14 Sep., 23:26, Vyacheslav Lanovets <xent...@gmail.com> wrote:

But I want to complain that boost::shared_ptr<> has tricky internals
to provide suport for user-defined delete policies. And these tricks
are based on virtual calls what just crashes our application.

I'd like you to think: do we really need these cool features of
shared_ptr<> or we need simple bullet-proof _standard_ ref-counted
smart pointer?

1) The current standard draft already proposes to add std::shared_ptr
which has basically the same interface (and a compatible semantic) to
boost::shared_ptr (but the wording does not mandate the above
described implementation technique). Since the current boost
implementation would not violate the proposed interface, this would
be a possible implementation provided by your favourite vendor.
If this happens you can complain at your vendor, not at boost - so
what would be the difference for you?

2) What we really need are standardized dynamic libraries, see
e.g.

http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2407.html

Greetings from Bremen,

Daniel Kr?gler

--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]