I think it'd be cool to notice, and properly report, write errors, rather than
silently ignoring them.
Back when lwall was asking for things we wanted perl6 to do, I asked to be able
to wrap builtins specifically so I could
use Fatal qw(print).
Yes, perl5 often ignores write errors, but no, I
> On 16 Jun 2017, at 14:10, Jan Ingvoldstad wrote:
>
> On Fri, Jun 16, 2017 at 12:13 PM, Elizabeth Mattijsen wrote:
>
> Failed to write bytes to filehandle: Broken pipe
> in block at -e line 1
>
> So it would appear this got fixed by the synchronous IO refactor, and will be
> available in
On Fri, Jun 16, 2017 at 12:13 PM, Elizabeth Mattijsen
wrote:
>
>
> Failed to write bytes to filehandle: Broken pipe
> in block at -e line 1
>
> So it would appear this got fixed by the synchronous IO refactor, and will
> be available in the 2017.06 release, which is scheduled for tomorrow.
>
>
> On 16 Jun 2017, at 08:34, Sean McAfee wrote:
>
> I see at
>
> http://www.moarvm.com/releases.html
>
> ...that as of the 2017.03 release, Perl 6 "ignores SIGPIPE by default." I
> discovered this for myself when I piped a program that generates unlimited
I see at
http://www.moarvm.com/releases.html
...that as of the 2017.03 release, Perl 6 "ignores SIGPIPE by default." I
discovered this for myself when I piped a program that generates unlimited
output to the head utility, and the program did not exit when head was
finished. Simp
