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

[Andrew J. Schorr]

On Sat, Mar 25, 2017 at 08:16:08PM +0100, FERRIEUX Alexandre - IMT/OLN wrote:
> OK, so, on behalf of the worst behavior (of a few non-posix oddball
> OSes), you'd rather sacrifice the unix instance of ... awk ? All of
> this for a "hard to maintain" 3-liner
..
> # define SIGPIPE_EXIT_CODE   1 /* my OS is too dumb to tolerate more than one 
> bit here *:
...
> Seriously...

No need to get snippy. We are discussing the best way to resolve this issue.
You obviously feel very strongly that the fate of humanity depends on the 141
exit code from a broken pipe. I personally never check the exit code other than
for success (zero) vs failure (non-zero).