[
https://issues.apache.org/jira/browse/COR-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282047#comment-14282047
]
jan iversen commented on COR-26:
--------------------------------
The link you provided points to all threads ?
I was trying to find Apache Commons API, but I could not find any C library
only java. If I missed the C implementation can you please provide a link.
I am all for that we use as much as commons as we can, as long as it is in C
(like APR).
If the Commons API is a slim library in C then the choice is yours. We have to
watch out for memory footprint, some of these libraries (not APR) use quite a
lot of memory.
If commons api is in java and you want to use the ideas and methods from the
java implementation you have a clear +1 from me.
We need to update the scripts to load these packages. I suggest to load them as
source and have a Cmake file to build them (I volunteer to make the cmake file,
so it fits with the other cmake files).
> 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)
