I love having long options because it provides a better description of what the options are when someone views your program for the first time. It simply is a great user interface tool when someone comes across on of your scripts for the first time.

I start every new command line perl script with this template...

#!/usr/bin/perl use strict; use warnings; use Getopt::Long; use Pod::Usage; Getopt::Long::Configure("no_ignore_case"); GetOptions( 'h|help'=> sub { pod2usage( { -verbose => 1, -input => \*DATA } ); exit; +}, 'H|man' => sub { pod2usage( { -verbose => 2, -input => \*DATA } ); exit; +}, ); __DATA__ head1 NAME =head1 SYNOPSIS Options: -h --help Display this help -H --man Display detailed help (examples) =head1 EXAMPLES =head2 First Example...

-biz-


In reply to Re^2: Use Getopt::Long even if you don't think you need to by jbisbee
in thread Use Getopt::Long even if you don't think you need to by ysth

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.