Yes, there is almost always a workaround (as of late I've grown fond of storing a custom operation object in an array and spawning invocation operations for each with my own concurrency metric and pushing them onto the queue though that obviously defeats much of the point of the API) but one should not rely on workarounds.
-rob. On Dec 17, 2008, at 11:14 AM, Keith Duncan wrote:
On 17 Dec 2008, at 15:41, Jean-Daniel Dupas wrote:because there's absolutely no way to guarantee that only a single NSOperationQueueexists in your processCouldn't you swizzle +[NSOperationQueue alloc] to return a singleton? Sure it's a hack, but a simple one that can be #ifdefed out for post Leopard builds. And would fix the problem for now if you've already architected a project around operation queues.Keith _______________________________________________ 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/rob%40pinchmedia.com This email sent to r...@pinchmedia.com
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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