Parameter/Option management

For some time we've known that there is a limitation of the existing parameter management: if you have an option line like

command --foo bar

then the option parser will assume that bar is the value of the foo option, even if the foo option is boolean.

While setting up the OptionParser? object, it became clear that the reason for this limitation is that (a) the ParameterList? object is used to parse the command-line, but (b) ParameterList? doesn't know the types of the options.

This points to a fundamental design flaw of the ParameterSet/ParameterList? class structure. This needs to be reworked before the next major UTILIB release!!!