In your case, perhaps Getopt::Std will be just fine. This not to say that that other suggestions aren't fine also.
use Getopt::Std; my %opts; die "Usage $0 -m or -M #1 #2 #3..." if (!getopts( "mM", \%opts) || @ARGV !=0 || keys %opts != 2); CalculateMean() if $opts{m}; #@ARGV has just #1 #2 #3 ...now. CalculateMedian() if $opts{M};
getopts::Std take a string and a ref to a hash as args. The magic of getopts in its various flavors is that it removes the option and the parameter (if any) from @ARGV.
There is a syntax for this: "mf:" means that "-m" doesn't have an arg, but that "-f" does, like someprogram -m -f filename 1 2 3. In this case the %opts hash will have keys of "m" and "f". The value of $opts{m}=1, the value of $opts{f} = 'filename' and @ARGV = (1,2,3).
You can have things like -a -f filename 1 2 3 4 or -f filename -a 1 2 3 4. Of course if somebody types in: -a -f 1 2 3 4 filename, you have to figure out that "1" isn't a filename. Anyway getopts looks for essentially space separated tokens, -3 like +3. That's the way that a C program would get the args.
I hope this helped.
In reply to Re^3: Usage of flags in scripts
by Marshall
in thread Usage of flags in scripts
by jordandanford
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |