Handles parsing the ARGV in the command line and provides support for GetOpt compatible option definition. Provides a builder pattern implementation for creating shell option parsers. ### Options Named arguments come in two forms, long and short. Long arguments are preceded by two - and give a more verbose option name. i.e. `--version`. Short arguments are preceded by one - and are only one character long. They usually match with a long option, and provide a more terse alternative. ### Using Options Options can be defined with both long and short forms. By using ` aParser.addOption()` you can define new options. The name of the option is used as its long form, and you can supply an additional short form, with the `short` option. Short options should only be one letter long. Using more than one letter for a short option will raise an exception. Calling options can be done using syntax similar to most *nix command line tools. Long options cane either include an `=` or leave it out. `uim _command --connection default --name=something` Short options can be defined singly or in groups. `uim _command -cn` Short options can be combined into groups as seen above. Each letter in a group will be treated as a separate option. The previous example is equivalent to: `uim _command -c -n` Short options can also accept values: `uim _command -c default` ### Positional arguments If no positional arguments are defined, all of them will be parsed. If you define positional arguments any arguments greater than those defined will cause exceptions. Additionally you can declare arguments as optional, by setting the required param to false. ``` aParser.addArgument("model", ["required": false]); ``` ### Providing Help text By providing help text for your positional arguments and named arguments, the DConsoleOptionParser buildOptionParser can generate a help display for you. You can view the help for shells by using the `--help` or `-h` switch.