Here's code adapted from the Cookbook that may do what you want:
use IO::Handle;
pipe(READER, WRITER);
WRITER->autoflush(1);
if ($pid = fork) {
# if fork returned a PID, this must be the parent
close READER; # so the child can use it
print WRITER "Your message here, call 555-8467, extension $$!";
close WRITER;
waitpid($pid, 0); # let the kid die
} else {
# if $pid is empty, this must be the child
close WRITER; # so the parent can use it
my $line = <READER>;
print "What does this mean?\n\t>>$line<<\n";
close READER; # don't have to be explicit
exit;
}
The
close() is important because
fork tends to duplicate open filehandles between the parent and child. We take advantage of some of this, though.
I don't know how well it will work passing variables instead of explicit filehandle names to the pipe call. You might have better results with:
local *$read;
local *$write;
In reply to Re: why?
by chromatic
in thread why?
by iic
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.