Chris Nehren on 11 May 2011 16:58:33 -0700

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [Philadelphia-pm] GetOpt::Long::Descriptive or GetOpt::Simple?

On May 11, 2011, at 19:01 , Mark Gardner wrote:

> On Wed, May 11, 2011 at 5:21 PM, Randall A Sindlinger
> <> wrote:
>> I'd like to embed documentation into the options as I define them, similar to
>> the OptionParser in Python's optparse module.
> I've also had good luck with Getopt::Euclid, which parses out options
> processing out of the POD-formatted documentation for each option.

Euclid is dangerous Damianware (read: Damian abandonware) fueled by brittle crack and voodoo under the hood. Take a look at its innards and see if you still want to use it. Getopt::Simple apparently does bad things with soft references and doesn't use warnings: not things I feel comfortable with in a module so critical to my app development. By contrast, Getopt::Long::Descriptive is a confound/rjbs module, and having worked extensively with App::Cmd I can say that it's solid, mature code which can bend to pretty much whatever you want.

Take a look at for some good suggestions on how to go about choosing which CPAN library to use.

Thanks and best regards,
Chris Nehren

Philadelphia-pm mailing list