Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

optional arguments #31

Open
suntong opened this issue Apr 9, 2017 · 1 comment
Open

optional arguments #31

suntong opened this issue Apr 9, 2017 · 1 comment

Comments

@suntong
Copy link
Collaborator

suntong commented Apr 9, 2017

The GNU getopt supports optional arguments:

A long option normally begins with '--' followed by the long option
name. If the option has a required argument, it may be written
directly after the long option name, separated by '=', or as the next
argument (i.e. separated by whitespace on the command line). If the
option has an optional argument, it must be written directly after the
long option name, separated by '=', if present.

Would cli support optional arguments as well? If true, please make it clear of the following three stages:

  1. not specified
  2. specified but no argument
  3. specified and with argument

Thanks

@mkideal
Copy link
Owner

mkideal commented Apr 15, 2017

optional arguments supported but 0/1/2 stages not reported. I will add API later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants