I'm a big fan of using Getopt in my command line programs. What I've become a little dissatisfied with the organization of the flags and variables. I'm looking for some input here from the monks on organizational tips. I'll post a sample of the code style I normally use.
#!/usr/bin/perl
use strict;
use Getopt::Long;
my $showos=0;
my $showrel=0;
my $showarch=0;
my $showiface=0;
my $showhd=0;
my $showmem=0;
my $showuser=0;
GetOptions (
"os|o"=>\$showos,
"rel|r"=>\$showrel,
"arch|a"=>\$showarch,
"iface|i"=>\$showiface,
"hd|h"=>\$showhd,
"mem|m"=>\$showmem,
"user|u"=>\$showuser,
"all|A"=> sub { $showos = 1; $showrel = 1; $showarch = 1; $sho
+wiface = 1; $showhd = 1; $showmem = 1; $showuser = 1; },
"help|h" => sub { &help; exit 0; }
);
. . .
Maybe this is already the best pattern to use, but it just looks kind of ugly to me. Any ideas would be appreciated.
--
“For the Present is the point at which time touches eternity.” - CS Lewis
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.