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

Incorrect behaviour with short and long command name #60

Closed
ghost opened this issue Feb 28, 2013 · 4 comments
Closed

Incorrect behaviour with short and long command name #60

ghost opened this issue Feb 28, 2013 · 4 comments

Comments

@ghost
Copy link

ghost commented Feb 28, 2013

Good day, developer team!

Using last version of CommandLineParser library I found incorrect library behaviour. When I pass next parameters
-read ReadFileName
your library consider -read argument as -r command with ead parameter.
I am using test project from "demo" folder. Looks like in parsing process CommandLineParser process on first short option name, and than process long option name.

I attached screenshot. You can view parsing result in Watch 1 window.
CommandLineParser

@alexanderfast
Copy link
Collaborator

Isn't this the intended behaviour? I think youre supposed to be able to write -rReadFileName

@ghost
Copy link
Author

ghost commented Feb 28, 2013

I think this is incorrect behaviour. Because you able to use short command name or long command name. I can use -r ReadFileName or -read ReadFileName sytax.

@ghost
Copy link
Author

ghost commented Feb 28, 2013

Sorry. This is not bug. I use "-" charaters instead of "--" pair characters. I must use --read ReadFileName instead of -read ReadFileName.

@ghost ghost closed this as completed Feb 28, 2013
@gsscoder
Copy link
Owner

Anyway, thanks for using this project.

When needed, back here for help :))

This issue was closed.
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