Re: NSTask flaky about posting terminate notification, in 10.6
Re: NSTask flaky about posting terminate notification, in 10.6
- Subject: Re: NSTask flaky about posting terminate notification, in 10.6
- From: Jens Alfke <email@hidden>
- Date: Wed, 2 Sep 2009 15:39:36 -0700
On Sep 2, 2009, at 3:25 PM, Dave Keck wrote:
o Recently I've found myself rolling my own solutions to problems such
as yours, in order to guarantee its level of robustness.
I've been resisting giving up on NSTask, but it might be necessary. Is
your code open-source or otherwise available?
After a cursory read over your code, I'm wondering why you need to
wait for the process to exit, and couldn't just wait for a
notification to be sent and deal with it when the time comes
MYTask is just a general-purpose utility that can be called
asynchronously or synchronously. Murky calls it in both ways.
Asynchronous is better, of course, but it's also harder to write, so
there are synchronous calls left in the code. If I ever decide to make
Murky require 10.6, it'd be fun to fix that by using blocks.
—Jens_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden