Re: Unix Signals Delivered from Quitting Cocoa Apps?
Re: Unix Signals Delivered from Quitting Cocoa Apps?
- Subject: Re: Unix Signals Delivered from Quitting Cocoa Apps?
- From: aaron smith <email@hidden>
- Date: Mon, 13 Sep 2010 02:54:48 -0700
One more note about this. It does work as expected. But I am going to
take out the dependency of having that hardcoded "1" parameter - which
the child looks for so it only runs the cocoa app. I'll probably
change it to use named pipes. Then it won't depend on having arguments
correct.
On Mon, Sep 13, 2010 at 2:24 AM, aaron smith
<email@hidden> wrote:
> Thanks for the suggestions!
>
> Yeah sorry I was getting around to fixing that return NSApplication thing.
>
> here's another version that avoids higher level framework usage..
>
> http://pastebin.com/20W1ZD8r
>
> Does that look better?
>
>
> On Mon, Sep 13, 2010 at 1:38 AM, Ken Thomases <email@hidden> wrote:
>> On Sep 13, 2010, at 3:05 AM, aaron smith wrote:
>>
>>> Thanks for pointing that I can't use high level frameworks in a child.
>>> I'll set up everything I need for the execvp call before the actual
>>> fork.
>>
>> You haven't addressed the problem. I was not talking about the later fork(), but the first one. These two lines:
>>
>> pid_t child = fork();
>> if(child==0) return NSApplicationMain(argc,(const char **)argv);
>>
>> are untenable. You are running the bulk of the original application in a forked-but-not-exec'ed child process. Your whole approach to this issue is unworkable.
>>
>> Sorry,
>> Ken
>>
>>
>
_______________________________________________
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