Use a real option parser

[jaz303]

When I originally wrote phake I hand-rolled the command line option parser because PHP's getopt functions were useless and the only alternative was to pull in half of PEAR to get access to a better one. However, we're now living in the age of Composer/Packagist, and a cursory search showed there to be a number of independently maintained possible alternatives.

What are everyone's thoughts about switching to a more robust option parser? Does anybody have a preferred package?

[clue]

thoughts about switching to a more robust option parser?

+1

This will big a big step towards addressing #32.

Does anybody have a preferred package?

Not yet, but I'll see I can come up with a lightweight alternative.

[lalop]

what about using the symfony console component for input/output ?

[jaz303]

As long as it's modular/lightweight I'm all for it. I'll check it out

[lalop]

That cans be a good things.
And permit to easily add helpers like that http://symfony.com/doc/current/components/console/helpers/index.html

Open to help one this point, just ping me.

[sagikazarmark]

IMO Symfony Console is everything, but not lightview.

First of all: option parsing and the things called InputInterface and OutputInterface are not the same.

BTW "output": I prefer CLImate these days.

[sagikazarmark]

@jaz303 check this:

https://github.com/ulrichsg/getopt-php

[sagikazarmark]

or this:
https://github.com/nategood/commando

[sagikazarmark]

or this:
https://github.com/c9s/GetOptionKit

(probably this is the most robust one)

[jaz303]

Thank you for putting in the time to do this research. I'll check those out next week and hopefully integrate one.

[mamchenkov]

I'm all for it. Hopefully, the command line options can extend to tasks as well. Tasks often require parameters and it would be nice if there was a standard way for the task to specify which parameters are accepted, which are required, and to provide some basic validation (parameter types, for example).