There is a common mechanism for all descriptors, to check whether a descriptor is ready for reading/writing, please check out IO::Select.
The main point is to call can_read or can_write before you really go reading/writing. This way, you even don't need to bother blocking/non-blocking mode. More important, you gain a better control.
On the other hand, I attached a simple sample to show pipe:
parn.pl:
use strict;
use warnings;
$| ++;
print "Entering parn.pl...\n";
my $chld;
open($chld, "perl -w chld.pl|") || die "failed to open child process\n
+";
my @ready;
while (1) {
my $from_chld = <$chld>;
print $from_chld * 2, "\n";
}
chld.pl:
use strict;
use warnings;
$| ++;
while (<>) {
if ($_ < 100) {
print "$_";
}
}
Update: for getc, although it returns one char a time, but unfortunately, this only happens after return is hit. An alternative way is presented in perlfunc under getc.
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.