commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandeep Tamhankar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLI-216) Optional support for concatenated option in the DefaultParser
Date Tue, 21 Nov 2017 05:06:00 GMT

    [ https://issues.apache.org/jira/browse/CLI-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16260255#comment-16260255
] 

Sandeep Tamhankar commented on CLI-216:
---------------------------------------

In my application, I have multi-character short options. I'd like to require the user to specify
such options precisely; allowing substring matches will lead to my users' confusion. For example,
if I have {{-f}} and {{-foo}} options, and the user specifies {{-fao}}, I do *not* want it
interpreted as {{-f}} with value {{ao}}. I want parsing to fail.

This has one particular repercussion: the optional boolean arg that CLI-217 adds to the DefaultParser
constructor is arguably not the best way to set the partial-match setting. Maybe the constructor
should continue to have no args but there be some setters to set the parser settings; or maybe
have a DefaultParser.Builder class that has setters for config options. My point is that having
the constructor take simple boolean arguments is not scaleable.

> Optional support for concatenated option in the DefaultParser
> -------------------------------------------------------------
>
>                 Key: CLI-216
>                 URL: https://issues.apache.org/jira/browse/CLI-216
>             Project: Commons CLI
>          Issue Type: Improvement
>          Components: Parser
>    Affects Versions: 1.3
>            Reporter: Emmanuel Bourg
>
> DefaultParser supports the concatenated options of the PosixParser (i.e tar -zxvf), but
in many cases this behavior is not desirable. This should be made optional.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message