It's pretty easy to convince them. Just insist that instead of writing fragile code that blithely ignores error returns, they check and report them properly.
my $cmd = "cp $foo $bar";
my $r = system($cmd);
if ($r) {
if ($? == -1) {
die "failed to execute '$cmd': $!\n";
}
elsif ($? & 127) {
my $msg
= sprintf "'$cmd' failed with signal %d, %s coredump\n",
($? & 127), ($? & 128) ? 'with' : 'without';
die $msg;
}
else {
die "'$cmd' exited with value %d\n", $? >> 8;
}
}
This is based on the example code in perlfunc(1). Faced with writing all that just to get a correct error message on failure, any developer would prefer to encapsulate the code in some routine, called... oh, I don't know, perhaps copy()?
Now while File::Copy's interface is not as crufty as system()'s, you still have to check for errors explicitly:
copy($foo, $bar) or die "cannot copy $foo to $bar: $!";
But that's a big improvement for any programmer who wants to be lazy but still write correct code.
Others have mentioned the need to use multi-argument system(), otherwise your code will have (perhaps exploitable) bugs when passed filenames containing spaces or shell characters.
-
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.