• 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
Re: Follow-up: Cocoa thread-safety
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Follow-up: Cocoa thread-safety


  • Subject: Re: Follow-up: Cocoa thread-safety
  • From: Dustin Voss <email@hidden>
  • Date: Sun, 27 Oct 2002 13:51:44 -0800

On Saturday, October 26, 2002, at 09:00 AM, Steve Klingsporn wrote:

If I keep a reference to the main NSRunLoop, and call performSelectorWithOrder()
from the main thread, everything works fine. If I call performSelectorWithOrder()
from any other thread, the selector simply is not performed. For the "modes"
parameter, I've tried manually setting them, and calling NSRunLoop.allModes()
to get the NSArray of modes. No luck.

NSRunLoops are thread-specific. Each thread gets its own run loop. I doubt it it safe to call on one thread's run loop from another thread; if it were safe, Apple would not have needed to add those new functions.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
References: 
 >Re: Follow-up: Cocoa thread-safety (From: Steve Klingsporn <email@hidden>)

  • Prev by Date: Re: Max arguments for NSTask?
  • Next by Date: Re: Max arguments for NSTask?
  • Previous by thread: Re: Follow-up: Cocoa thread-safety
  • Next by thread: Re: Cocoa thread-safety
  • Index(es):
    • Date
    • Thread