On Fri, 17 Jun 2005 08:45:26 -0700 Eric Wilhelm <[EMAIL PROTECTED]> wrote: > Ok. Then my previous argument stands. If the --no- means "unset any > hard-coded or config-file defaults", then it shouldn't be evaluated in > command-line order.
Well, as I said, if you would like unordered options, simply put
"foo" and "no-foo" in 2 different variables seperately. It's just the
flexibility you accused on Getopt::Long that may solve your problem
in 2 lines, but not having to write a whole new module.
Getopt::Long::GetOptions(
"fish=s" => [EMAIL PROTECTED],
"no-fish" => \$opt_nofish,
);
@conf_fishes = qw() if $opt_nofish;
@fishes = (@conf_fishes, @opt_fishes);
--
Best regards,
imacat ^_*' <[EMAIL PROTECTED]>
PGP Key: http://www.imacat.idv.tw/me/pgpkey.txt
<<Woman's Voice>> News: http://www.wov.idv.tw/
Tavern IMACAT's: http://www.imacat.idv.tw/
TLUG List Manager: http://www.linux.org.tw/mailman/listinfo/tlug
pgpN0cxhOyIAb.pgp
Description: PGP signature
