From: Gavin Sinclair <gsinclair@...>
Date: 2005-12-29T14:37:54+09:00
Subject: Re: Command-line option parsing


Eric J. Roode wrote:
> mathew <meta@pobox.com> wrote in news:wjosf.9901$9e.8623
> @tornado.texas.rr.com:
>
> > Eric J. Roode wrote:
> >> GetoptLong suffers from being "the same old Getopt".
> >
> > Well, what do you expect from an options parser?  It's pretty much a
> > solved problem, and using the standard getopt algorithms has the
> > advantage that users know what to expect.
>
> Well... that's not *bad*, but I guess I had expected something a bit more
> ruby-like.  Whatever that means.  :-)

That's a good expectation to have.

You mention OptionParser has poor documentation.  While it's not
complete, I find the example at [1] is quite adequate.

[1]
http://ruby-doc.org/stdlib/libdoc/optparse/rdoc/classes/OptionParser.html

Gavin