[Top][All Lists]

[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: Sun, 26 Mar 2017 05:38:23 +0300

> Date: Sat, 25 Mar 2017 23:48:05 +0100
> From: FERRIEUX Alexandre - IMT/OLN <address@hidden>
> Cc: address@hidden
> Of course the 141 vs 1 is no big deal. But if it comes for free, what about 
> it ?
> By "for free" I mean an #ifdef appropriate to cover all of true unix. 
> Something like
>       #ifdef unix
>       # define SIGPIPE_EXIT_CODE (128|SIGPIPE)
>       #else
>       # define SIGPIPE_EXIT_CODE 1
>       #endif

This isn't guaranteed to produce 141 on every system, so you don't get
what you want except a small number of platforms.

AFAIK, Gawk attempts to provide a more or less portable environment,
and the above is against that goal.

reply via email to

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