Standardize command-line parameters

[markplagge]

When choosing command line options for ROSS, there are several options that have a logical space in them, such as "gvt interval", "clock rate", "lz4 knob", "avl size" and others. However, the flags are not consistent. Some flags have an underscore, while others have a dash. It would be great if they all used one or the other.

[nwolfey21]

Bump

[gonsie]

any opinion on which is better, underscore or dash? Does a standard exist for command line options in general?

[JohnPJenkins]

Dashes are used in unix land and don't require holding the shift key :).

While we're on the subject, specifying user parameters through tw_optdef spits out the warning "missing braces around initializer" (via -Wmissing-braces, enabled by -Wall), caused by the TWOPT_END macro not being within braces. I think we had this fix in before, but it may have been lost in the SR transition?

From: Elsa Gonsiorowski <notifications@github.commailto:notifications@github.com>
Reply-To: carothersc/ROSS <reply@reply.github.commailto:reply@reply.github.com>
Date: Wednesday, August 12, 2015 at 1:06 PM
To: carothersc/ROSS <ROSS@noreply.github.commailto:ROSS@noreply.github.com>
Subject: Re: [ROSS] Standardize command-line parameters (#59)

any opinion on which is better, underscore or dash? Does a standard exist for command line options?

—
Reply to this email directly or view it on GitHubhttps://github.com/carothersc/ROSS/issues/59#issuecomment-130395246.