On 31 Jan 09, at 19:15, Robert Marini wrote:
Easily reproduced doesn't always translate into guaranteed to occur. In my experience, using a single queue in your application is a sufficient safeguard as no system framework I've encountered causes an issue. That isn't to say that the API is without quirks but they can usually be adjusted to easily enough... (in short, one can endlessly debate whether or not it's safe to use NSOperationQueue or one can use it and ship a product a great deal quicker than if they hadn't and join a number of other applications churning data in large installation bases).
That's true. However, there are some surprisingly easy ways to end up with multiple queues - one example might be if one queue is associated with each document object in a document-based application. (In this case, the bug might manifest as rare crashes when multiple documents are open and "doing stuff".)
_______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
