jeffa is quite right...here's what I tend to do, since the next natural thing is to assign each option out into a meaningfully named scalar 
my %opts;
getopts("d:a:s:e:", \%opt);
my $Directory = $opts{'d'} || '/home/maverick';
my $Address   = $opts{'a'} || 'somewhere@overtherainbow.com';
my $Silent    = $opts{'s'} || 0;
my $Extended  = $opts{'e'} || 0;

[download]
This way I don't have to remember what's in $opts{'d'} and neither does whoever reads my code later. Plus the defaults are really easy to spot.

/\/\averick
perl -l -e "eval pack('h*','072796e6470272f2c5f2c5166756279636b672');"

In reply to Re: Setting default values in getopts by maverick
in thread Setting default values in getopts by neilwatson

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.