On May 9, 2016, at 11:26 , Carl Hoefs <[email protected]> wrote: > > Alas, there appear to be no GCD dispatch queue introspection functions, > specifically to find out what is executing (if anything) and what's waiting > in the queue. Or did I overlook something?
Also, no, I don’t think so. There is dispatch_get/set_context, but the documentation is unclear as to whether these work on queued blocks. Cancelling GCD operations is also a bit more primitive than you would like. The other thing that NSOperationQueue can do that I don’t think GCD can do is limit the “width” of a concurrent queue (AFAIK). If you need to manipulate the queue operations themselves, this does seem like something of a code smell in regard to GCD. In that case, NSOperationQueue is probably a better choice. Perhaps it’s worth going back to that, in the hope that your crashes get more frequent, and you can investigate what really causes them. _______________________________________________ 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]
