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

[alexandre.ferrieux]

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 ...

> > >  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, which is somehow funny in the light of your saying that the 
exit status in Windows has much more precision than a single bit.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.