Honore de Baka

• About: I comment about Perl.

Recent Actions

• Commented on Mystery Line in Proc Input in Perl 6
  It looks like `k8temp` last byte is a "\n" (0x0a). If lines is implemented as a simple split, this seems to be an expected behavior. The weird thing is that the docs ( http://docs.perl6.org/type/Str#routine_lines ) seems to say that the...
• Commented on CPAN Day - 317 Uploads and 21 Guns
  Disclaimer : What's coming next is a rant. You're free to call me a troll, or simply ignore me on the basis that I have no contributions on CPAN and that non-contributors just have the right to shut up. But...

Comment Threads

• Aaron Baugher commented on Mystery Line in Proc Input in Perl 6

  I notice that if I save the output of k8temp into a file (which does end with a \n), then have my script read from that file with:

  my @l = "temps".IO.lines;
  @.perl.say;

  Then the array only gets two elements, and no extra third with an empty string.

• Liz commented on Mystery Line in Proc Input in Perl 6

  Looking into it, it appears there is a different logic in setting EOF between getting a handle from a file, or from a process. The latter appears to be setting EOF too late, hence the extra empty line.

  Determining cause of action now...

• Aaron Baugher commented on Mystery Line in Proc Input in Perl 6

  Yeah, I tracked both cases to the same line in IO::Handle which calls `nqp::p6box_s(nqp::readlinefh($!PIO)).chomp`, and hadn't figured out yet where to go from there, but I guess it's at the NQP layer.

• Rob Hoelz commented on Mystery Line in Proc Input in Perl 6

  Tobias Leich went ahead and fixed the bug today!

• Aaron Baugher commented on Mystery Line in Proc Input in Perl 6

  Cool, I'll have to look and see how; I haven't gotten into the underlying stuff yet.