Here's another suggestion. You can use Getopt and POD (plain ond documentation). All of your command line options are stored in a single hash for easy lookup.
use strict;
use warnings;
use Getopt::Long;
use Pod::Usage;
# Process and validate the command line options in @ARGV.
my %options;
my $parse = new Getopt::Long::Parser;
if (!($parse->getoptions('infile=s', \($options{infile}),
'outfile=s', \($options{outfile}),
'help', \($options{help})))) {
help();
}
if (not defined($options{infile})) {
help();
}
sub help
{
pod2usage(0);
}
__END__
=head1 NAME
A.pl - Creates A file
=head1 SYNOPSIS
A.pl [options]
Options:
--infile=[file]
--help
=over 3
=item B<--infile -i=[file]>
A file that is used for input, wildcards are allowed
=item B<--outfile -o=[file]>
Optional parameter for the output file
=item B<--help -h -?>
Print a brief help message and exits.
=head1 DESCRIPTION
B<This program> creates a A files.
=cut
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.