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
<> vs <STDIN> is OS specific #4446
Comments
From madison@transmeta.comI wrote a simple STDIN inline filter that puts a command in When I then read from <> (as opposed to <STDIN>), I get nothing -------------------------------------------------- stdin_filter("sort"); Perl Info
|
From The RT System itselftestpl open FOO,"<&STDIN" || die "can't open <&STDIN: $!\n"; run as 'perl testpl <bob' solaris: FOO=3 linux: FOO=3 |
2 similar comments
From The RT System itselftestpl open FOO,"<&STDIN" || die "can't open <&STDIN: $!\n"; run as 'perl testpl <bob' solaris: FOO=3 linux: FOO=3 |
From The RT System itselftestpl open FOO,"<&STDIN" || die "can't open <&STDIN: $!\n"; run as 'perl testpl <bob' solaris: FOO=3 linux: FOO=3 |
From The RT System itselftest message from the perlbugtron |
From @jkeenan
I ran the attached program, commenting out first one 'while' loop and So either I misunderstood what I was supposed to be doing, or the Thank you very much. |
From @sciurius"James E Keenan via RT" <perlbug-followup@perl.org> writes:
It works here as expected (both 'while' variants). Perl 5.12 and 5.14 on Fedora 14. -- Johan |
From @HugmeirOn Tue Nov 22 23:39:13 2011, jv wrote:
Also working as expected here, Ubuntu 11.10 & Solaris 10. I vote to |
From @cpansproutOn Sat Apr 28 00:08:01 2012, Hugmeir wrote:
Do we mark this as stalled, as no one can reproduce it, or resolved, -- Father Chrysostomos |
@cpansprout - Status changed from 'open' to 'resolved' |
From @rjbs* Father Chrysostomos via RT <perlbug-followup@perl.org> [2012-04-28T03:29:25]
For the record: resolved. "stalled" is "this is definitely a bug we want to -- |
Migrated from rt.perl.org#7747 (status was 'resolved')
Searchable as RT7747$
The text was updated successfully, but these errors were encountered: