On Nov 19, 2009, at 2:54 PM, Colin Deasy wrote: > I have a shared thread that is used to process multiple asynchronous tasks. > But at some point, a task may need to 'pause' its execution, and cannot exit > its method and wait to be re-called, how can I do this?
They're not really asynchronous tasks if they need to block. You might try to refactor your design so nothing blocks — this usually involves converting local state inside a method, into state in an object's instance variables. If you can limit yourself to 10.6, using blocks can help a lot in this. > In that method, where a 'pause' instance is brought about, can I use > something like the following to wait, but not block the run loop? > while(condition)[[NSRunLoop currentRunLoop] runMode:NSDefaultRunLoopMode > beforeDate:[NSDate dateWithTimeIntervalFromNow:0.01]]; The short answer is "yes". The full answer is that while this is tempting, and it can be made to work, it enables complicated forms of re-entrancy that can produce very unexpected results that are hard to debug. The problem is that external state can change out from underneath your handler while it's waiting like this, as other handlers run. You can even get the same handler invoked in nested form. Or you can get the opposite problem, where the outer handler sets some state (such as acquiring a lock) that breaks other nested handlers when they try to access the same state. Several times I've managed to catch a crash, then scrolled down the call stack and gone "oh shit!" as I see the multiple layers of handlers. I would recommend you not go this route. —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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
