Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[Discussion] About the CLI interface #18
After taking a look at SW, I noticed that you use single-dash for options. (
I guess you based this on the Windows way of handling options? I'm used to
Regarding this point, I just wanted to make sure the behavior you are using is a Windows convention or if you designed it yourself. (I think it may be more common for developers to use the Unix standard I just described, though)
Another thing I wanted to mention is regarding the notion of "command" in the CLI.
Reading your answer for #16, I noticed you made
The following options seem to have this issue:
It may not be very useful feedback but it made me think for a bit so I thought I could share my thoughts with you.
CLI is an issue. I did not find anything suitable for my needs yet.
Current implementation is from clang. It allows -single-dash long options.
It is /option1 /option2 :)
Because I did not accept final CLI options implementation or library, there will be such mess like now.
I'm against it. Command list MUST be populated rarely and not for small commands like this.
I disagree from an user experience point of view, it seems odd to use an option without a command while others will print
PS: I just noticed that it is
It's because the option is then called
My bad but it was just an example.
I guess you've got a point, there. (Even though I find this convention a bit strange but who am I to judge?)
One more note here.