New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apparent improper handling of SIGPIPE #6351
Comments
From frettled@gmail.comAccording to a brief mail discussion on perl6-users For the sake of bug record keeping, here's the relevant snippet of the On Fri, Jun 16, 2017 at 12:13 PM, Elizabeth Mattijsen wrote:
This appears to be only a partial fix with an unexpected outcome. awk, Perl 5, Ruby, etc. do not generate errors for similar use of PS: I have not installed the latest Rakudo myself, this just caught my -- |
From @LeontOn Tue, 20 Jun 2017 06:12:54 -0700, jani wrote:
The problem with the unix default SIGPIPE handling is that while it's very useful for command-line applications, it's most annoying for pretty much anything else (in particular networking applications). Regardless of the default, this needs an easy to use switch to toggle the behavior. Leon |
The RT System itself - Status changed from 'new' to 'open' |
Migrated from rt.perl.org#131608 (status was 'open')
Searchable as RT131608$
The text was updated successfully, but these errors were encountered: