[RFC] Standardize the option names in nvq++

At the moment, we have a lot of command line options in nvq++ that take both the form -my-option and --my-option. We also have options that are strictly only -my-single-option or --my-double-option.

While that all functions correctly, there hasn't really been any coherent guidance on this. As such users may be surprised when the driver accepts one spelling or another then rejects something that seems very similar.

Some strategies:

• Use 1 dash for distinct options. Self-explanatory.
• Use 1 dash short options with (optional) 2 dash long spelling of equivalent options. -o and --object-file for instance.
  • Long options without short equivalents could either be 1 or 2 dashes
• Use 1 dash for all options and use a prefix letter to categorize related groups. For example, clang and gcc use -f<option> for controls relating to optimizations, etc., and -W<option> to control diagnostics.
• Use 1 dash only with one letter, 2 dashes for everything with more than 1 letter.
• Keep adding options in an ad hoc way, as we're doing now.
• other proposals?

Start with the nvq++ command-line options and compare the accepted spellings described in the RFC. Review the listed naming strategies and existing discussion before proposing a direction; done means the project has an agreed, coherent convention for current and future options.