From @AlexDaniel

So, in this bug report we will be attempting to read $*IN when we are already
reading it because of the -n flag.

$*IN.get() hangs if the file is listed as an argument, but does not hang if it is piped

Command​:
perl6 -ne 'say $*IN.get' /etc/passwd
Or
perl6 -ne 'say $*IN.lines' /etc/passwd

Result​:
(nothing, it hangs!)

Interestingly, it does not hang if instead of listing the files you actually pipe something​:

Command​:
perl6 -ne 'say $*IN.get' < /etc/passwd

Result​:
(prints a bunch of stuff)

Now, obviously, it is a little bit weird for the user to try to read from $*IN when -n flag is
in place, but there is at least one documented case of accidental use :) http://irclog.perlgeek.de/perl6/2016-05-01#i_12416462

Also, since it does not hang if proper STDIN is present, I think that it should work.

From @AlexDaniel

See also​: https://rt-archive.perl.org/perl6/Ticket/Display.html?id=128047

From @geekosaur

On Sun, May 1, 2016 at 7​:11 AM, Alex Jakimenko <perl6-bugs-followup@​perl.org

wrote​:

Now, obviously, it is a little bit weird for the user to try to read from
$*IN when -n

Not that weird. Let the loop read chunk headers, and read/process the rest
of the chunk in the middle of the loop. It's used that way in perl5 and
other languages fairly often.

--
brandon s allbery kf8nh sine nomine associates
allbery.b@​gmail.com ballbery@​sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net

The RT System itself - Status changed from 'new' to 'open'

From @zoffixznet

The code you provided doesn't hang, it waits for input from $*IN. If you type enough (or press ^D), the program will run. -n flag sets $_ to each line of the given file.

Would you please clarify what the problematic issue is?

From @AlexDaniel

On 2016-07-09 10​:51​:13, cpan@​zoffix.com wrote​:

The code you provided doesn't hang, it waits for input from $*IN. If
you type enough (or press ^D), the program will run. -n flag sets $_
to each line of the given file.

Would you please clarify what the problematic issue is?

Right! Right… For some reason I was assuming that stdin will be substituted with file contents, hmm.

If it is supposed to be this way, then yeah, there's no problem, and we can probably reject this. But do we need a test?

From @zoffixznet

If there's no bug, then I'll close this without tests.

If any general tests aren't complete for the methods involved in the report, they will be added as part of my upcoming work to increase roast coverage.

--
Cheers,
ZZ | https://twitter.com/zoffix

@zoffixznet - Status changed from 'open' to 'rejected'