For one-time throw away tasks, maybe. This is expensive code though, particularly if there are tons and tons of files to be appended to. You are spawning shells for each iteration of the loop. These in turn fire off copy (which may or may not be a builtin to your shell) which in turn has to perform the same open, print, close logic your script would do anyway.

Besides, it's not very perlish. {g}

But, on an off topic for those who are saying "don't close your file, let the scope take care of it", please think some about maintainability. Someday a n00b will see your code and not understand how the scope issues work. They'll just think "oh, I guess you don't have to worry about closing things".
{NULE}
--
http://www.nule.org

In reply to Re: Re: foreach not working as I expected by {NULE}
in thread foreach not working as I expected by ellem

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.