On Oct 3, 2013, at 2:04 PM, Ken Thomases <[email protected]> wrote:
> Well, you've gone from requesting the ability to assign a queue to a run loop > to assuming that all run loops would have queues. You’re right. I think I was implicitly imagining it would be like [NSRunLoop currentRunLoop] in that it would create one the first time it was asked. > And your code already dispatches to the calling thread's run loop, right? > Why not, if dispatch_get_current_queue() returns NULL, fall back to the > current approach of targeting the run loop? I have a vague memory of trying this some time ago and running into trouble; but of course I don’t remember exactly what went wrong. But in light of Mike’s explanation of target queues and “it’s dispatch queues all the way down”, I can see why getting the current queue isn’t a good approach. :/ —Jens _______________________________________________ Cocoa-dev mailing list ([email protected]) 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 [email protected]
