On Mon, 9 May 2005 14:05:10 +0100, "Avis, Ed" <[EMAIL PROTECTED]> wrote:
> I know that Getopt::Long accepts options at any place in the command > line; it would be consistent and useful for Getopt::Std to do the same. No, it would not, because then the Std (for STANDARD) would not be STANDARD anymore. This is the whole reason why there is Getopt::Long. This is also exactly the reason why I never use Getopt::Std, but I *do* have nopermute as one of my default options in Getopt::Long. Most of the *options* supported in Getopt::Long are just to please all people that want things in a non-standard way. Perl's way is TMTOWTDI, so is Getopt's Getopt::Std for the (old and traditional) standard, Getopt::Long to fullfill every other wish you miss in Getopt::Std. Please keep Getopt::Std standard. -- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using Perl 5.6.2, 5.8.0, 5.8.5, & 5.9.2 on HP-UX 10.20, 11.00 & 11.11, AIX 4.3 & 5.2, SuSE 9.2 & 9.3, and Cygwin. http://www.cmve.net/~merijn Smoking perl: http://www.test-smoke.org, perl QA: http://qa.perl.org reports to: [EMAIL PROTECTED], [email protected]
