bug-gawk
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH]


From: Eli Zaretskii
Subject: Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH]
Date: Sat, 25 Mar 2017 22:40:46 +0300

> Date: Sat, 25 Mar 2017 15:21:22 -0400
> From: "Andrew J. Schorr" <address@hidden>
> Cc: address@hidden
> 
> You obviously feel very strongly that the fate of humanity depends on the 141
> exit code from a broken pipe.

It isn't even 141 on all systems.  E.g., the Windows value for EPIPE
is 32, so you will get 160 instead.

Why is it so important to know Gawk exited due to a broken pipe, given
that Gawk explicitly avoids exposing that, and for a reason?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]