corinthia-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (COR-26) Recommend standard getopt_longs for the utilities
Date Sun, 18 Jan 2015 19:18:34 GMT

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

Dennis E. Hamilton commented on COR-26:
---------------------------------------

I'm into that sort of thing.

I think it would be useful to have it at a library level for use by as many command-line tools
we come up with.  Not certain whether this would lead to another external dependency or not.

I will look into this.  I think I would look at transposing the Apache Commons version first,
simply because of licensing.  There might be a more-direct solution in C already, though.

> Recommend standard getopt_longs for the utilities
> -------------------------------------------------
>
>                 Key: COR-26
>                 URL: https://issues.apache.org/jira/browse/COR-26
>             Project: Corinthia
>          Issue Type: Improvement
>          Components: Consumers - dftest
>            Reporter: Dennis E. Hamilton
>             Fix For: 0.5
>
>
> It is recommended that the command-line utilities provided by Corinthia use a common
getopt model with single-letter options, verbose word options and common shared options (--version,
--help, etc.).  stdin, stdout, and stderr should be redirectable (via the shell) and the utilities
should work with pipes (with appropriate encoding caveats).
> The same flavors can be used for all platforms, with filenames given in platform-specific
form (and "..." where needed) but parameters and options the same across platforms.
> The GNU getopt_long approach is widely-used.  http://en.wikipedia.org/wiki/Getopt



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message