Any command that takes STDIN will work for piping into. cp is not one of those. I would read the man page for any command that you'll want to call directly from a Perl program. There are slight differences between platforms that can cause problems if you depend on them. You shouldn't be calling programs that you don't know the behaviour of.

One of the Perl ways of doing this without decent error checking. It works, but I see some changes need to be made before I'd allow it on my system. 
use strict;
use warnings;
use File::Copy;

  my $file1 = shift || die "No args!\n";
  my $file2 = shift || die "Second file please?\n";

  copy("$file1","$file2");

[download]
I still recommend more manual reading

In reply to Re: Piping into system commands by lemming
in thread Piping into system commands by Vortacist

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.