[
https://issues.apache.org/jira/browse/CLI-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713602#action_12713602
]
Jim Jagielski commented on CLI-181:
-----------------------------------
I was thinking about adding a sort of "format string" which defines the type of
options the user wants to support; eg:
"-a foo --apple=banana -flag"
CLI then determines the option formats that need to be supported via scanning
that string and then uses those aspects of the parser. So by folding all 3
parsers into 1 super parser, this would be easier. Of course, anything that
removes the need for end-users to have to worry about "which parser to use" is
goodness ;)
> Unified parser
> --------------
>
> Key: CLI-181
> URL: https://issues.apache.org/jira/browse/CLI-181
> Project: Commons CLI
> Issue Type: Improvement
> Components: Parser
> Reporter: Emmanuel Bourg
> Fix For: 1.3
>
>
> The 3 parsers available in the API create an unnecessary complexity for the
> users and for the developers maintaining the code. I suggest deprecating them
> in favor of a unified parser supporting the features of the others.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
