From: Ed Howland on 27 Feb 2010 23:05
I like the style of Trollop. I started doing something similar, but it
is a generator, that just happens to have a part of it that is a DSL
for option generation. Right now, it just wraps GetOptLong. It could
just as easily wrap TrollOp for the options part. I like the fact that
it can live as a file in lib/.
However, I'd like to package my stuff as a gem, and TrollOp would have
to be packaged in a template folder in there. Not sure if that is the
best way to handle it, or to require TrollOp as a gem dependency.
On Wed, Sep 30, 2009 at 2:19 PM, William Morgan
> Dear Rubyists,
> I have released Trollop 1.15. This release is dedicated to my fellow wrinkled,
> old-fashioned, out-moded throwbacks who still use the commandline instead of
> clicking on their webapp.
> Trollop is a commandline option parser for Ruby that just gets out of your way.
> One line of code per option is all you need to write. For that, you get a nice
> automatically-generated help page, robust option parsing, subcommand support,
> and sensible defaults for everything you don't specify.
> It's one file. If you don't want to gem install it, just copy the damn thing
> into your lib/ directory and get off my lawn.
> Main page: http://trollop.rubyforge.org
> Release announcements and comments: http://all-thing.net/label/trollop/
> == FEATURES/PROBLEMS
> - Dirt-simple usage.
> - Sensible defaults. No tweaking necessary, much tweaking possible.
> - Support for long options, short options, short option bundling, and
> automatic type validation and conversion.
> - Support for subcommands.
> - Automatic help message generation, wrapped to current screen width.
> - Lots of unit tests.
> == REQUIREMENTS
> * A burning desire to write less code.
> == CHANGES in 1.15
> * Don't raise an exception when out of short arguments (thanks to Rafael
> Sevilla for pointing out how dumb this behavior was).
> William <wmorgan-ruby-talk(a)masanjin.net>