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

[Eli Zaretskii]

> Date: Sat, 25 Mar 2017 23:37:49 +0100
> From: FERRIEUX Alexandre - IMT/OLN <address@hidden>
> CC: "Andrew J. Schorr" <address@hidden>, <address@hidden>
> 
> On 25/03/2017 20:40, Eli Zaretskii wrote:
> > 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?
> 
> For the same reason that we're insisting that it exits in the first place.

I don't see how this explains it: we insist that it exits because it
has no place to continue writing, that's all.

> In other words: there are situations where you want to prevent it from 
> exiting (so be it) ; and there are situations 
> where you want it to exit (the default behavior), plus some cleanup. Once 
> this cleanup is done, there is no added value 
> in muddying the water with an uninformative exit status.

We do provide information in the form of the exit status, it clearly
tells that the exit was due to an error.

IOW, my question still stands.