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 Mon, 19 Jan 2015 00:35:34 GMT

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

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

Dave Fisher provided more about this suggestion on a thread at http://mail-archives.apache.org/mod_mbox/incubator-corinthia-dev/201501.mbox/browser

I am interested in the Apache Commons API because of the data structure and the rules by which
it is used to "steer" parsing of the command-line parameters and also provide an automatic
help text for incorrect command lines.  This form might be easier to localize as well.  (I
would be cagy about localizing the option words, as opposed to the text of the description
of the parameter options.)

The Apache Portable Runtime (APR) apr_getopt_init() and apr_getopt_long() functions are in
C and the use of those runtime functions and the lower-level libraries they depend on is an
interesting consideration.  This may apply generally for Corinthia, since it is C based at
the run-time library-support level.

For both of these libraries, the Apache License is already applicable with respect to any
derivatives, including translations, so their can be full source-code provision in the Corinthia
source tree in all cases.

> 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
>            Assignee: 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