This kind of redundancy has never really bothered me. I
usually use Getopt::Long in conjunction with Pod::Usage and
my 'skeleton' usually looks like:
use Getopt::Long;
use Pod::Usage;
our ($user,$pass,$numb,$help);
GetOptions(
'user|u=s' => \$user,
'pass|p=s' => \$pass,
'numb|n=i' => \$numb,
'help|h|?' => \$help,
);
$numb ||= 42;
pod2usage(-verbose=>2) if $help;
pod2usage(-verbose=>1) unless $user and $pass;
__END__
Considering that the variables used to hold user options are
being shared across two (or more) packages, this doesn't
seem overly redundant to me. But that's just me. ;)
UPDATE: hmmm, here is something evil:
our ($user,$pass,$numb,$help);
my @tmpl = (
'user|u=s',
'pass|p=s',
'numb|n=i',
'help|h|?',
);
@tmpl = map {"'$_' => \\\$@{[(split('\|',$_))[0]]},"} @tmpl;
eval "GetOptions(@tmpl);";
jeffa
L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.