That is because
tie only is working on Perl IO. A
system command hands the file descriptor for STDOUT
to the command being launched, which knows nothing about
Perl's IO.
The same gotcha exists for working with C extensions that
do their own printing.
For one solution you can do a piped open like this:
use IPC::Open3;
sub piped_cmd {
local *TO;
local *FROM;
open3 (\*TO, \*FROM, \*FROM, "perl") or die "Cannot launch perl: $!"
+;
print TO @_, "\n__END__\n";
local $/;
<FROM>;
}
(That is portable, Windows and Unix.)
Note that doing things that way does not give access to
various things that you have defined in your script. If you
want that you are probably out of luck because all of the
methods that I know of for IO games (select, tie, etc)
work at the Perl level, and leave the C file-descriptors
alone. But then when you call system the program works
by file descriptor. :-(
This could be construed as a bug.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.