That looks pretty good as it is. The File::Find usage looks fine.

I think your @ARGV handling is unnecessary. You have already arranged for command line options to set the default modes. Those options are removed from @ARGV when Getopt::Long parses them. You could arrange for @ARGV to be a list of directories to apply to if you wished.

Kudos for including a usage function. You may be interested in Pod::Usage. It automatically extracts usage functions from the pod - which I recommend you add to your script. You can then read the pod with perldoc myscript and you can easily extract a man.1 page from your literate perl on installation.

Good work, I wouldn't guess you'd been using perl such a short time.

After Compline,
Zaxo

In reply to Re: How would you go about it? by Zaxo
in thread How would you go about it? by pcassell

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.