Re: -[NSThread start] blocks ?!?
Re: -[NSThread start] blocks ?!?
- Subject: Re: -[NSThread start] blocks ?!?
- From: Charles Srstka <email@hidden>
- Date: Sun, 27 Sep 2015 23:37:15 -0500
> On Sep 27, 2015, at 11:18 PM, Jens Alfke <email@hidden> wrote:
>
>> On Sep 27, 2015, at 8:49 PM, Jerry Krinock <email@hidden <mailto:email@hidden>> wrote:
>>
>> My point is that if we can’t at least rely on -[NSThread start] returning before the secondary starts, there is no way for a seconary thread to call back to the main thread without possibility of deadlock.
>
> Why?
>
> You do realize that people managed to use NSThread successfully for years before GCD was introduced.
>
> But if you don't like NSThread's behavior, just use GCD instead.
1. The fact that NSThread is now apparently using dispatch semaphores internally suggests that it is no longer implemented the same way that it was back when it was the preferred threading mechanism on OS X.
2. The fact that NSThread hasn’t been the preferred threading mechanism for quite some years suggests that it may no longer be as thoroughly tested by Apple as well as GCD is.
I’d definitely move to GCD, if it were me.
Charles
_______________________________________________
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