My typical command line parsing goes something like this:
use vars qw/ $opt_help $opt_one $opt_two $opt_config /;
sub parseCommandLine();
parseCommandLine();
......
......
sub parseCommandLine() {
&getOptions( 'help|h', 'config|c=s', 'one', 'two=s' ) or $opt_help
+= 1;
if( defined( $opt_help ) ) {
&printUsage();
exit(0);
}
if( defined( $opt_config ) ) {
&parse_config( $opt_config );
}
if( defined( $opt_one )) {
# do extra setup required for option 1
} else {
$opt_one = 'default_opt_one';
}
unless( defined( $opt_two ) ) {
$opt_two = 'default_opt_two';
}
# Do stuff needed for option 2.
}
sub parse_config( ) {
my $config_file = shift();
# read file
# use file to set $opt_one, $opt_two
}
Hope this helps...Untested code of course :)
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.