Oh Brothers and Sisters in perl I beg the fruits of your wisdom.
I have a simple script I am using to get the hang of IPC::open3. When I do the open I wrap it in an eval and die if it failed. The die however does not happen until after the rest of the script is done.
#!/usr/bin/perl
use strict;
use warnings;
use IPC::Open3;
my($in, $out, $err, $pid);
open( $out, ">&STDOUT" ) or
die "Can't dup STDOUT to OUTPUT: $!\n";
open( $err, ">&STDERR" ) or
die "Can't dup STDERR to OUTERR: $!\n";
eval { $pid = open3($in, $out, $err, @ARGV) };
die "open3 gave trouble: $@\n" if $@;
print "It is running\n";
close $in;
print "stdout:\n";
print while <$out>;
close $out;
print "stderr:\n";
print while <$err>;
close $err;
__END__
# this is expected
./open3 echo "Hello World"
It is running
stdout:
Hello World
stderr:
# this is confusing the proverbial out of me
./open3 nosuchcommand
It is running
stdout:
stderr:
open3 gave trouble: open3: exec of nosuchcommand failed at ./open3 lin
+e 15
# The die obviosly ran but the code did not die,
# ran to completion regardless then printed the error
Cheers, R.
Pereant, qui ante nos nostra dixerunt!
-
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.
|