[
https://issues.apache.org/jira/browse/UIMA-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13654453#comment-13654453
]
Marshall Schor commented on UIMA-2874:
--------------------------------------
I would be interested in the rationale for what you favor. Things which move
toward uniformity, and make more clear the available distinctions among the
various approaches, seem like a good thing. This style seems similar to some
Google API styles; I recall some of those APIs also supported chaining, similar
to StringBuilders "append" method - each call returned the original object, to
which you could add another setXXX method.
The previous approach is using the more traditional Java style of multi-arg
constuctors, with alternate shorter forms (fewer arguments).
The style of having individual setXXX methods is more verbose - it essentially
gives a way to associate a "keyword" with the parameter. So instead of
* new Serializer(true, false), you have
* (new Serializer()).setXXX(true).setYYY(false)
which seems a good trade-off for maintainability in the future, given that Java
(today) doesn't support keyword arguments. Although I suppose one could write
* new Serializer(/*XXX*/ true, /*YYY*/ false)
but I've not seen that style used much.
> binary compression APIs in CAS
> ------------------------------
>
> Key: UIMA-2874
> URL: https://issues.apache.org/jira/browse/UIMA-2874
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: 2.4.1SDK
>
>
> Rationalize the CASImpl binary compression APIs; add to the CAS Apis.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
