• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
NSOperation and threadDictionary
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NSOperation and threadDictionary


  • Subject: NSOperation and threadDictionary
  • From: Rick Mann <email@hidden>
  • Date: Tue, 21 Sep 2010 15:52:26 -0700

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

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:

This email sent to email@hidden

  • Follow-Ups:
    • Re: NSOperation and threadDictionary
      • From: Julien Poissonnier <email@hidden>
  • Prev by Date: Re: AXUIElementPostKeyboardEvent and Carbon applications
  • Next by Date: Re: Access object from another view
  • Previous by thread: Re: AXUIElementPostKeyboardEvent and Carbon applications
  • Next by thread: Re: NSOperation and threadDictionary
  • Index(es):
    • Date
    • Thread