I assume that this is a simplified example and that you are trying to understand the issue rather looking for a workaround, but in just in case... you could read the DATA before forking...
use strict;
use warnings;
my @data = <DATA>;
my $pid= fork();
die unless defined $pid;
if ($pid == 0) {
print "Start c\n";
for (@data) {
print "c: $_"; sleep 1;
}
print "stop c\n";
}
else {
print "Start p\n";
for (@data) {
print "p: $_"; sleep 1;
}
print "stop p\n";
}
__DATA__
a
b
c
d
e
I admit that I do not know either what the fork/DATA problem is. If you put in a sleep statement before the loop you can control whether the parent or the child reads the DATA segment but this is not helpful either.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|