Converted to a subroutine, make the exec safer, optionally capture STDERR, lexical filehandle:
=head3 safe_pipe
safe_pipe [ options, ] command, input
my $results = safe_pipe [ 'command', 'arg' ], @input;
my @results = safe_pipe [ 'command', 'arg' ], @input;
my $results = safe_pipe { capture_err => 1 }, [ 'command', 'arg' ], @
+input;
Pipe data to a shell command safely (without touching a command line)
+and
retrieve the results.
Options:
=over 4
=item capture_err
If true, STDERR will also be captured and included in returned results
+.
=back
=cut
sub safe_pipe {
my $opt = {};
$opt = shift if 'HASH' eq ref($_[0]);
my $command = shift;
my ($RESULT, @x);
$command = [$command] unless ref $command;
if (open $RESULT, "-|") { # original process: receiver (reads $RESUL
+T)
@x = <$RESULT>;
}
else {
if (open STDIN, "-|") { # child: processor (reads STDIN, writes ST
+DOUT)
open STDERR, ">&STDOUT" or die "Can't dup STDOUT: $!" if $$opt{c
+apture_err};
exec { $$command[0] } @$command;
die "Cannot exec @$command: $!";
}
else { # grandchild: sender (writes STDOUT)
print @_;
exit 0;
}
}
wantarray ? @x : join('', @x);
}
-
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.