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

[Eli Zaretskii]

> Date: Sun, 9 Apr 2017 12:49:51 +0200
> From: <address@hidden>
> CC: <address@hidden>, <address@hidden>
> 
> On 09/04/2017 11:40, Eli Zaretskii wrote:
> >> >  Anybody looking 0xC000014B up with a header grep or a google search 
> >> > will land on "pipe broken".
> > As I explained earlier, the issue is not with grepping Windows headers
> > (which end-users likely won't have installed), the issue is with other
> > programs that interpret these exit codes when invoking Gawk as a
> > sub-process.  None of them know about the value you propose, while the
> > value I used_is_  known.
> 
> How many of them will stop and not use Google ? Seriously ...

Programs don't use Google.  They use values encoded in their source
code.

> >> >  So, "invalid handle" is simply not applicable at all.
> > I can only say that I disagree, and I explained why.
> 
> I can only say you purposefully lose important information

Once again, I disagree.