Eric Wilhelm <[EMAIL PROTECTED]> writes: > 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.
Good deduction, but the premise does not hold. --no- does not mean "unset any [...] defaults", it means: set the option value to 'false'. >>And b) mixing options and arguments, where "--foo arg1 --no-foo arg2" >>means that arg1 is processed with --foo and arg2 with --no-foo. > > This is not something I'm trying to address. That's okay. There are several Getopt:: modules that implement a simplified subset of Getopt::Long for various reasons. -- Johan
