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
open2 acts very strange when STDOUT is redirected. #12748
Comments
From xungeng@gmail.comCreated by xungeng@gmail.comsee this example: #*STDOUT = IO::Handle->new; for (1..3) { *STDOUT = IO::Handle->new; for (1..3) { the difference between foo and bar is only that STDOUT redirected or not. when STDOUT is redirected, open2 make the child process write to the old Perl Info
|
From @iabynOn Tue, Jan 29, 2013 at 10:38:14PM -0800, Xungeng Lee wrote:
Well for stdout, IPC::Open3 (which IPC::Open2 calls out to) does pipe(\*Reader, \*FOO); i.e. it dups the file handle of the pipe to whatever file handle STDOUT I don't understand Open3.pm enough to decide whether it's unreasonable for -- |
The RT System itself - Status changed from 'new' to 'open' |
Migrated from rt.perl.org#116589 (status was 'open')
Searchable as RT116589$
The text was updated successfully, but these errors were encountered: