Use nopt to parse command-line options #68
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to add new options like "--newline-separator" in the future, without messing up with the existing options, I switched option parsing to nopt, which should make it easier to detect options anywhere in the arguments (currently, anything passed after --code, --file or --ast would be considered a "snippet" as part of the positional arguments).
This change is mostly retrocompatible for correct usage, supporting a few new cases like
luamin "a = 5" --code
(--code
can be put after the positional arguments), and detecting compact forms likeluamin -ch
forluamin -c -h
(obviously a bad example since it will ignore -c and just print help, but will be useful when we add more options, compatible with -c, -f and -a).