<rant>
I really hate the stupid suggestions of adding 'strict' and 'warnings' if they do not solve the problem presented.

Problems should be presented with as minimal code as necessary to show the problem. The OP did that. Slapping the three lines you suggested on to it would just make the code larger, drawing away the attention from the problem. Don't scold at the OP for doing the right thing.

And would have gained nothing - except to stop mindless responses like yours.

Yeah, yeah, someone will say, but it's good advice anyway. Sure it is. And so are the other 255 points from Damians newest book. Should we post a list of 256 good advices on every problem posted here?
</rant>

In reply to Re^2: File::Copy a bug? by Anonymous Monk
in thread File::Copy a bug? by moked

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.