> As I've said before, if GetOptions() could be a few-lines wrapper
> around the $opt = Getopt::Long->new()... $opt->get([EMAIL PROTECTED]) dance,
> this allows the author (of what will most likely be a module if they
> want to parse something besides ARGV) to design their own entry
> point if need be.
I'm puzzled. Basically, you suggest that it is okay to craft your own
entry point
sub MyGetOptions { # [EMAIL PROTECTED], @opts
my $argv = shift;
Getopt::Long->new(@_)->get($argv);
}
while you always disapproved of something like
sub MyGetOptions { # [EMAIL PROTECTED], @opts
local(@ARGV) = @{shift};
GetOptions(@_);
}
> There's not a lot of reason to add new functionality into the old
> interface because anybody using the new functionality (by
> definition) requires the new version.
I can fully agree with that.
-- Johan
