I have to strongly disagree with your first point. You just need to fix your copy of Perl to expand wildcards. It sucks that ActiveState doesn't make this easy, but there are instructions in one of the FAQs. Actually, I just stuff a @ARGV=map{glob($_)}@ARGV if $^O=~/^MSWin/; at the front of scripts that take a list of file names.

It would really suck if people started following your specific advice of hardcoding <*> so that scripts could never be run on a subset of files or files from more than one directory.

See File::Spec for more advice on making scripts portable.

        - tye (but my friends call me "Tye")

In reply to (tye)Re: Cross platform compatability Part 1: Shells and Files by tye
in thread Cross platform compatability Part 1: Shells and Files by jepri

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.