Exact semantics of NSThread executation states?
Exact semantics of NSThread executation states?
- Subject: Exact semantics of NSThread executation states?
- From: Sean McBride <email@hidden>
- Date: Tue, 12 Jul 2016 17:52:58 -0400
- Organization: Rogue Research Inc.
Hi all,
NSThread has at least 3 execution state properties: executing, finished, cancelled. Alas, the docs don't say much about what they mean beyond circular definitions like "A Boolean value that indicates whether the receiver is executing".
I have code where I create an NSThread, add a runloop source, then invoke "start" on the thread. I have assumed that once I invoke "start" that "isExecuting" should give YES. Literally:
[myThread start];
assert([myThread isExecuting]);
On 10.11.5 and earlier this *seems* to always be true, but on 10.12b2 it's not. I'm trying to understand if my assumption was wrong or if it's an OS bug.
Thanks,
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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