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;
    }
}

[download]
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: $!";

[download]
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.

In reply to Re: File::Copy versus cp/mv by ed
in thread File::Copy versus cp/mv by mce

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.