|
| From: | FERRIEUX Alexandre - IMT/OLN |
| Subject: | Re: [bug-gawk] Behavior of fflush with SIGPIPE on stdout [PATCH] |
| Date: | Sat, 25 Mar 2017 23:37:49 +0100 |
| User-agent: | Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111113 Thunderbird/8.0 |
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.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.
| [Prev in Thread] | Current Thread | [Next in Thread] |