comment on

Hi, one thing not to do is to disable strict and warnings!

After reenabling:

parent: 12158
parent 12158
    child 12159
    child 12160
    child 12161
<<<<<<<<<<<<<<<<<<<121591216012161
    child 12160
    child 12159
    child 12161
print() on closed filehandle WRITER at 1206479.pl line 29.
print() on closed filehandle WRITER at 1206479.pl line 29.
print() on closed filehandle WRITER at 1206479.pl line 29.
parent 12158
readline() on closed filehandle READER at 1206479.pl line 20.
    child 12160
Use of uninitialized value $line in chomp at 1206479.pl line 20.
print() on closed filehandle WRITER at 1206479.pl line 29.
Use of uninitialized value $line in concatenation (.) or string at 120
+6479.pl line 21.
<<<<<<<<<<<<<<<<<<<
[download]

Fix the errors, don't silence the warnings!

The way forward always starts with a minimal test.

In reply to Re: Getting messages from child processes via pipes by 1nickt
in thread Getting messages from child processes via pipes by Frizoker

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.


laziness, impatience, and hubris
	PerlMonks