Re: -[NSThread start] blocks ?!?
Re: -[NSThread start] blocks ?!?
- Subject: Re: -[NSThread start] blocks ?!?
- From: Jerry Krinock <email@hidden>
- Date: Sun, 27 Sep 2015 20:49:31 -0700
On 2015 Sep 27, at 17:01, John Daniel <email@hidden> wrote:
> There is no way to tell what is causing the deadlock without knowing exactly what is happening relating to:
> 1) instance
> 2) beginWithInfo:
> 3) info
Thank you, John. You are referring to what my secondary thread is doing. 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. It’s a defect in NSThread.
> Data sharing using serial queues is safer and more robust by design.
OK, if it is a defect in NSThread, GCD might not have this defect. I’ll consider that. Thank you.
Jerry
_______________________________________________
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