[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: replacing process sentinels and filters with hooks
|
From: |
Paul Eggert |
|
Subject: |
Re: replacing process sentinels and filters with hooks |
|
Date: |
Mon, 01 Oct 2012 07:42:15 -0700 |
|
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120912 Thunderbird/15.0.1 |
On 10/01/2012 06:14 AM, Christopher Monsanto wrote:
> Each hook takes one argument,
> which has one of the following forms:
>
> '(input <string>)
> '(signal <signalcode> <core dump flag>)
> '(exit <exitcode>)
Overall this sounds like a nice cleanup.
One relatively-minor comment about those forms.
I take it that the (signal ...) pattern is when
waitpid reports WIFSIGNALED and the (exit ...)
pattern for WIFEXITED. But what happens for
WIFSTOPPED and WIFCONTINUED?