On Wednesday, June 19, 2002, at 09:57 , Timothy Johnson wrote:
[..]
> But just for
> the sake of argument, here's one approach:
On a more serious note, you cats may want to try
perldoc -m Getopt::Std
and walk through what is in the code - since it
has a really nice structure of the form
while (@ARGV && ($_ = $ARGV[0]) =~ /^-(.)(.*)/) {
($first,$rest) = ($1,$2);
if (/^--$/) { # early exit if --
shift @ARGV;
last;
}
.....
}
unless (ref $hash) {
local $Exporter::ExportLevel = 1;
import Getopt::Std;
}
Which may help you resolve how traditionally the
walk through @ARGV has been handled.
remember that the '-m' arg to perldoc lets you
view the whole of the Module and not merely the POD.
The same adventure throught
perldoc -m Getopt::Long
will also show you the funk on the inside of that
module - and perchance give you a better way to
go about evaluating which is the more sensical solution.
ciao
drieux
---
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
