Jayesh Patel wrote:
Agreed, though Getopt::Long still allows for the short options, so it is really a matter of preference, you can even alias a long and a short option to the same resulting value so that if at some point in your organization one of your people like long options while most of the rest like short, then they can both be happy. Long and short can also be intermixed on the same command line. And key=val can also be replaced with just --key val or even -k val or in a bundle, -kvalmval2... etc. Its also a standard module, which means you are about 98% (or more) guaranteed to have it everywhere....So to make my script dummy proof, I am trying to find easy ways of parsing the input the getopts ignores. I guess what I am looking for is a getopt::std that saves the part that it ignores in a special variable. Does anyone do this ? I don't like the getopt::long because I use many options. Also with the -- & something=something, things look ugly and the developers like things simple.
Just some thoughts,
http://danconia.org
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
