-----Original Message----- I think this might help:
http://www.boost.org/doc/libs/1_39_0/libs/smart_ptr/shared_ptr.htm#Thre adSafety
It covers shared_ptr only, though.
Regards,
Roland
I had read that. " A shared_ptr instance can be "read" (accessed using only const operations) simultaneously by multiple threads. Different shared_ptr instances can be "written to" (accessed using mutable operations such as operator= or reset) simultaneosly by multiple threads (even when these instances are copies, and share the same reference count underneath.)" was instructive. That's what I need. But I was specifically wondering about the mix of weak_ptr's. I guess mine is more complicated because it can do lazy copy on write, but still the effect of making the unowned pointer getting ownership at the same time as other threads are releasing all the existing owners was an issue of specific importance. I implemented a "sticky zero" non-blocking counter for the purpose. I want to make sure that the Boost implementation can do this robustly and efficiently, too. And perhaps point out that weak_ptr's need thread issue documentation too. TradeStation Group, Inc. is a publicly-traded holding company (NASDAQ GS: TRAD) of three operating subsidiaries, TradeStation Securities, Inc. (Member NYSE, FINRA, SIPC and NFA), TradeStation Technologies, Inc., a trading software and subscription company, and TradeStation Europe Limited, a United Kingdom, FSA-authorized introducing brokerage firm. None of these companies provides trading or investment advice, recommendations or endorsements of any kind. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.