On Sep 22, 2010, at 12:52 AM, Rick Mann wrote: > Does iOS (and Mac OS X) clean up thread-local storage upon the completion of > an NSOperation? It seems dangerous to rely on every operation to clean up its > own mess. It also seems that an NSOperation should be able to pretend that it > owns the thread on which it's running, and not have to worry about whatever a > previous operation running on that thread might've done to the TLS. > > I read the NSOperation and NSOperationQueue docs, as well as the docs for > -[NSThread threadDictionary], but none of it mentions this topic. > > I can experiment to find out, but would like to know what others know about > this. > > Thanks, > Rick >
I don't know what happens to the threadDictionary when an NSOperationQueue "recycles" a thread, but the Concurrency Programming Guide states that you should avoid per-thread storage and consider the thread owned by the NSOperationQueue, not the NSOperation: http://developer.apple.com/library/ios/#documentation/General/Conceptual/ConcurrencyProgrammingGuide/OperationObjects/OperationObjects.html%23//apple_ref/doc/uid/TP40008091-CH101-SW27 -Julien_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
