On Thu, Aug 5, 2010 at 10:10 AM, Jens Alfke <j...@mooseyard.com> wrote: > What I’m guessing is that running a delayed block does not count as an “input > source”. That’s kind of frustrating, because it makes the runloop’s behavior > highly dependent on internal details of framework classes — in this case, how > was I to know that NSTask used a block and not an input source to handle > this? And presumably that means the behavior has changed in 10.6, which would > explain some weird NSTask related problems I’ve seen over the past year.
It's not just blocks—old-fashioned delayed performs don't cause the runloop to exit either. Here's a code snippet that exhibits the same behavior: http://gist.github.com/510055#file_delayed_perform.m --Kyle Sluder _______________________________________________ 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
