> On Oct 3, 2013, at 6:22 PM, Charles Srstka <[email protected]> wrote: > > The problem I see with queue arguments is that there are two types of queues > that people might be using — dispatch_queue_t and NSOperationQueue — and > there doesn't seem to be a way to convert one into the other. So if you > design your API to take an NSOperationQueue argument and your caller is using > dispatch queues, or vice-versa, then your caller is up a creek, unless you go > to the trouble to create two versions of each API, one for each type of queue.
It has been implied to me that the implementation of NSOperationQueue is less than stellar, and you might do best to avoid it whenever possible. For what it’s worth, if you break inside of a block running within an NSOperationQueue, you will always find yourself running on a global async queue. This might be an artifact of an NSOpQ’s internal dispatch queue targeting the main async queue, or it may be a sign that NSOpQ does not maintain a 1:1 mapping with a dispatch queue. --Kyle Sluder _______________________________________________ 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]
