[2.0] Multiple getopt issues. #384

Closed
SaberUK opened this Issue Dec 17, 2012 · 2 comments

Comments

Projects
None yet
2 participants
@SaberUK
Contributor

SaberUK commented Dec 17, 2012

  1. The getopt_long call checks for :f: instead of :c:f: which results in the short -c argument not being recognised.
  2. If you specify an invalid parameter with one - it mistakenly shows the previous argument as invalid.
  3. This might not be an issue but there is a reference to getopt_long_only in the switch block, is this no longer needed?
@attilamolnar

This comment has been minimized.

Show comment
Hide comment
@attilamolnar

attilamolnar Feb 17, 2013

Member
@attilamolnar

This comment has been minimized.

Show comment
Hide comment
@attilamolnar

attilamolnar Mar 25, 2013

Member

-c is now accepted, the other issues are scheduled for fixing in 2.2

Member

attilamolnar commented Mar 25, 2013

-c is now accepted, the other issues are scheduled for fixing in 2.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment