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
perlvar should mention STDIN, STDOUT, STDERR #13090
Comments
From @rjbsCreated by @rjbsperlvar.pod documents ARGV and ARGVOUT but not STDOUT, STDIN, and STDERR, Even if only by cross-reference, these should be documented in perlvar. Perl Info
|
From @ikegamiOn Sun, Jul 7, 2013 at 10:08 PM, Ricardo SIGNES
I tried to refer someone asking about @ISA to perlvar, but it wasn't |
The RT System itself - Status changed from 'new' to 'open' |
From @rjbsYes, if nothing else, an entry for @ISA that cross-references would be welcome. |
From @kentfredricThat might also be a good place to note that STD{IN,OUT,ERR} are |
From @ikegamiOn Tue, Jul 16, 2013 at 7:31 PM, Kent Fredric via RT <
Interesting. use strict; Output:
With every instance of FILE changed to STDOUT:
|
From @kentfredricYeah, in my experience, this was the most surprising part of win32 IO You think because you can redirect IO on unix, and you can do it on But this little detail is the basic reason it doesn't work, and this is The only way I know of that lets you handle this on Win32 in real time https://metacpan.org/module/Win32::Job use Win32::Job; And my testing demonstrates you can also do $job->spawn($execpath, $stringifed_arglist, { And the behaviour will be as expected ( try doing that without |
Migrated from rt.perl.org#118797 (status was 'open')
Searchable as RT118797$
The text was updated successfully, but these errors were encountered: