On Jun 14, 2008, at 9:12 PM, Bill Bumgarner wrote:
As well, no amount of locking will make a non-thread-safe object thread-safe unless you absolutely positively know that only your code (and only your code protected by the locks) contain the only reference to said object.
In the general case you wouldn't even be safe if this was the case, since that object could in turn modify shared mutable state in a thread-unsafe manner.
The bottom line is that you have to understand what you're doing, and you have to follow the thread safety rules outlined in the documentation.
j o a r _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
