Esteban,

The commandline parser produces an option dictionary (keys are long option names and values are the option values) and a collection of arguments. You provide a specification for the options (short name, whether or not options are required/optional or not expected) ... quite convenient.

Dale


On Thu, Jul 24, 2014 at 7:16 AM, Esteban A. Maringolo <emaringolo@gmail.com> wrote:
2014-07-24 11:07 GMT-03:00 Dale Henrichs <dale.henrichs@gemtalksystems.com>:

> My only wish is that CommandLine had better getopts support - I have a posix
> getopts commandline parser implementation that iI use for tODE that I'd be
> willing to share ... hint hint:).

Altough I'm used to Pharo's command line handlers now, it would be
great to have "standard" command line arguments.


Esteban A. Maringolo