On Sun, Apr 06, 2003 at 11:32:38PM +0200, Johan Vromans wrote: > > Currently they do not work with unprepared Getopt:: scripts. So it is > > not a security consideration that they won't work until the script is > > minimally modified. It should be enough to do one-place modification > > > > $Getopt::Std::HELP_VERSION_AWARE = 1; > > > > to change the behaviour to be standard-conforming. > > For Getopt::Long I use a much simpler approach: when the program uses > the appropriate version in the 'use' statement, it gets the new > features. Otherwise not. So if a program uses > > use Getopt::Long 2.33; > > it knows what it is asking for, and gets it. IMO, this is a very bad idea. The version-requirement should denominate the version such that the program *can't work* with versions below this; not that some features may be less convenient than without this version. Your suggestion helps with backward-compatibility of GO::L with older scripts; not with backward-compatibility of scripts with older GO::L. IlyaThread Previous | Thread Next