| Mark Gardner on 23 May 2011 13:23:52 -0700 |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
| Re: [Philadelphia-pm] GetOpt::Long::Descriptive or GetOpt::Simple? |
On Wed, May 11, 2011 at 7:58 PM, Chris Nehren <c.nehren/phl@shadowcat.co.uk> wrote: > On May 11, 2011, at 19:01 , Mark Gardner wrote: > >> On Wed, May 11, 2011 at 5:21 PM, Randall A Sindlinger >> <rsindlin+pm@seas.upenn.edu> 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. Do you think it could be rehabilitated? I.e., is the basic idea sound and could conceivably work without all the scary Damianisms? Also to be fair, Kevin Galinsky picked up maintenance late last year. It's not exactly abandoned, though I don't envy him. _______________________________________________ Philadelphia-pm mailing list Philadelphia-pm@pm.org http://mail.pm.org/mailman/listinfo/philadelphia-pm