command line interface conventions and best practices

Patrick Venture venture at google.com
Thu Feb 27 03:54:02 AEDT 2020


On Wed, Feb 26, 2020 at 7:57 AM Brad Bishop <bradleyb at fuzziesquirrel.com> wrote:
>
> Does anyone have a favorite reference that outlines de-facto command line
> interface conventions and best practices?  Things like e.g. long options
> should have two dashes, options should not have capital letters, etc?

There has been a push to using cli11 instead of each repo wrapping
getopts, but it's not required.

https://github.com/openbmc/docs/blob/master/anti-patterns.md#custom-argumentparser-object

>
> thanks!
>
> -brad


More information about the openbmc mailing list