Re: NSNotificationQueue & NSOperationQueue thread death
Re: NSNotificationQueue & NSOperationQueue thread death
- Subject: Re: NSNotificationQueue & NSOperationQueue thread death
- From: "A.M." <email@hidden>
- Date: Wed, 6 May 2009 12:01:17 -0400
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On May 6, 2009, at 11:49 AM, Jonathon Kuo wrote:
On May 4, 2009, at 8:12 PM, Ken Thomases wrote Re: 'A couple
NSRunLoop questions':
Every thread has exactly one run loop associated with it. You
don't create run loops nor do you remove them.
On May 5, 2009, at 9:24 PM, Michael Ash wrote Re:
'NSNotificationQueue & NSOperationQueue thread death':
Background threads, whether directly managed by you or indirectly
created by NSOperationQueue, do not use a runloop by default.
Sorry for my newb confusion. I know that these are different words
from different authors, but I'm having trouble reconciling these two
statements. How could a thread not have or use a runloop? Nothing on
it would ever execute...?
Any thread can have an NSRunLoop- it's just an object stored in thread-
specific data. Whether it spins or not (via its run... variants) is a
separate matter. When the runloop isn't "used", it isn't spinning, so
it will not respond to runloop events.
Cheers,
M
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (Darwin)
iEYEARECAAYFAkoBtFAACgkQqVAj6JpR7t5eRwCfVZ4tJj2s2CuO8n5wWCEuUNUp
P9sAoJlp4VrRDllCqLFpz+Cv4A59RxWL
=Poah
-----END PGP SIGNATURE-----
_______________________________________________
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