I use Getopts:;Long to parse command line arguments, and Pod::usage to display the POD documentation which is in the same file.
use POSIX qw{strftime};
use Getop:;Long;
use Pod::Usage;
my %options = (date => strftime( %Y-%m-%d);
Getopts( \%options, 'date=s', 'help', 'man' )
or pod2usage( { '-message' => 'Error processing command line args',
+
'-verbose' => 0,
'-exitval' => 1,
});
pod2usage( { '-verbose' => 1 }) if exists $options{help};
pod2usage( { '-verbose' => 2 }) if exists $options{man};
__END__
=head1 NAME
myprog - Use it to demo Getopt::Long and Pod::Usage
=head1 SYNOPSIS
myprog [-date yyyy-mm-dd] [-help] --man'
=head1 ARGUMENTS
=over 4
=item -date yyyy-mm-dd
The date to process. If not specified, today's date is used.
=item -help
Display a brief summary of the documentation, but not as brief
as shown for a command line argument error.
=item -man
Display complete man page.
=back
=head1 DESCRIPTION
This is what the program does, and how it works.
=head1 AUTHOR
me
=cut
As Occam said: Entia non sunt multiplicanda praeter necessitatem.
-
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.
|