Re^9: Use Getopt::Long even if you don't think you need to

Oddly enough, long options are almost the last thing I'd think of if I were listing the advantages of Getopt::Long.

To summarise, Tom C advocated the use of GO::Long over GO::Std--just in case.

You're advocating GO::Long--but not for the benefit of using long options.

Then, by all means, post your list of GO::Long "advantages", and let me debunk them one by one.

I'd suggest you reread Tom C's post (and maybe some of the others in this thread) with that perspective in mind, since I think you have seriously missed the point(s).

I just did.

I don't believe I missed his point, I just vehemently disagree with it.
I stand by my assessment above that long options are a far worse "slip, slip, slippery slope" than even a hand-rolled options parser.
I see no advantages to GO::Long over GO::Std if you are not going to use long options.
I see futurism as the modern day curse of software development.
I don't drive around one-up in an empty V10 pick-up truck on a daily basis, on the off-chance I might see a grand piano going cheap in a yard sale.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Comment on Re^9: Use Getopt::Long even if you don't think you need to

Replies are listed 'Best First'.
Re^10: Use Getopt::Long even if you don't think you need to by Anonymous Monk on Jan 18, 2012 at 11:26 UTC
FWIW, at minimum GetOpt::Std doc is too short, GetOpt::Long doc is more useful	[reply]