I'm going to try to remember this trick: 
{
    my %opt;
    getopts("hf:d:") || die HELP();

    sub opt_h { exists $opt{h} ? 1 : 0 }
    sub opt_f { exists $opt{f} ? 1 : 0 }
    sub opt_d { exists $opt{d} ? 1 : 0 }
}

[download]
 But if a given option takes an argument, wouldn't this be the way to go: 
{
    my %opt;
    getopts("hf:d:") || die HELP();

    sub opt_h { exists $opt{h} ? 1 : 0 }
    sub opt_f { exists $opt{f} ? $opt{f} : '' }
    sub opt_d { exists $opt{d} ? $opt{d} : '' }
}
if ( opt_f eq "foo" ) {
   ...
}
# usw, etc.

[download]
There's just that little issue about remembering to leave off the $ sigil when testing the options -- some habits are hard to unlearn (but "use strict" will cover that).

In reply to Re: A better usage of getopts by graff
in thread Referencing built-ins by Ovid

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.