Okay, a close approximation to system(1,...) for less fortunate builds of Perl is:
sub spawn
{
my( $cmd )= @_;
die "Usage: spawn($cmdLine) or spawn([$cmd,@args])"
if 1 != @_;
die "You don't need this; use system(1,...) instead."
if $^O =~ /win32/i; # Not an accurate test
my $cpid= fork();
die "Can't fork: $!\n";
if ! defined $cpid;
return $cpid
if $cpid;
if( ! ref $cmd ) {
exec( $cmd );
} elsif( 1 == @$cmd ) {
$cmd= $cmd->[0];
exec( $cmd $cmd );
} else {
exec( @$cmd );
}
die "exec failed: $!\n";
}
But note that system(1,...) has some non-trivial advantages still; I didn't replicate the "pipe to child process for making 'exec fails' cases" saner.
So you can use spawn($cmd) in place of system(1,$cmd) in the code I provided in the previous node. I didn't write spawn() to handle Win32 because it was a quick hack.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Outside of code tags, you may need to use entities for some characters:
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|