Re: Using IPC::Open3 instead of backtick operator

Hi rcrews,

without any critics, my programs use IPC::Cmd:

use strict;
use warnings;
use IPC::Cmd qw( run );

my $tool = 'tar';
my $cmd = [ $tool, 'xvzf', $in_filename ];
my $buffer = '';
my @out = run( command => $cmd,
          buffer => \$buffer,
          verbose => 1 );
die "Error extracting $in_filename: $buffer" unless $out[0];
[download]

Have fun!

Comment on Re: Using IPC::Open3 instead of backtick operator Download Code

Replies are listed 'Best First'.
Re^2: Using IPC::Open3 instead of backtick operator by ikegami (Patriarch) on Jun 10, 2016 at 15:58 UTC
This is the equivalent of doing `no warnings;`. It simply silences the message without addressing the issue (preventing error log from being filled with child's STDERR output). If your goal is simply to circumvent `perlcritic`, it provides far better ways of doing that.	[reply] [d/l] [select]
Re^3: Using IPC::Open3 instead of backtick operator by RonW (Parson) on Jun 10, 2016 at 17:54 UTC
Depending on configuration, IPC::Cmd will use either IPC::Run or IPC:Open3, so will capture STDERR as well as STDOUT. Called with 1 buffer, IPC::Cmd will put both STDOUT and STDERR in that buffer. Called in list context, it will return seperate buffers for STDOUT and STDERR.	[reply]
Re^4: Using IPC::Open3 instead of backtick operator by ikegami (Patriarch) on Jun 10, 2016 at 18:18 UTC
`use strict; use warnings; use IPC::Cmd qw( run ); my $tool = 'tar'; my $cmd = [ 'perl', '-e', 'warn "TEST FAILED IF YOU SEE THIS\n"' ]; my $buffer = ''; my @out = run( command => $cmd, buffer => \$buffer, verbose => 1 );` [download] `$ perl z.pl Running [perl -e warn "TEST FAILED IF YOU SEE THIS\n"]... TEST FAILED IF YOU SEE THIS` [download] However, one simply has to remove `verbose => 1` to make this a solution.	[reply] [d/l] [select]