> On Sep 27, 2015, at 11:18 PM, Jens Alfke <j...@mooseyard.com> wrote: > >> On Sep 27, 2015, at 8:49 PM, Jerry Krinock <je...@ieee.org >> <mailto:je...@ieee.org>> 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 (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
