On Sat, 5 Nov 2005, Daniel Berger wrote:

> Hi all,
> 
> I'm pleased to announce the release of getopt-1.3.0.  This release includes a
        [...]
> == How does it work
> It's similar to the old Getoptlong class, but it's less verbose, more flexible
> and (*shock*) it returns a hash.
> 
> == Synopsis
> require "getopt/long"
> include Getopt
> 
> opts = Long.getopts(
>    [ "--name",    "-n", REQUIRED ],
>    [ "--age",     "-a", OPTIONAL ],
>    [ "--more",    "-m", INCREMENT],
>    [ "--verbose", "-v", BOOLEAN]
> )
> 
> # User passes "--name dan --age=35 -m -m -v"

Will one be able to write that as
   -mmv --name dan --age=35
or not?  I expect it makes parsing trickier.  I don't do it for
single letter options that take parameters except 
tar -cvf tarfile -
so I could live without it.

Thank you.  Simplifying the interface is usually the right thing to
do :-)

        Thank you,
        Hugh