commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gilles (Commented) (JIRA)" <>
Subject [jira] [Commented] (MATH-707) Naming confusion
Date Wed, 08 Feb 2012 16:52:59 GMT


Gilles commented on MATH-707:

The lack of symmetry is inherent in the check: For "SimplePointChecker", the check is the
same (on the "point", a {{double[]}}), whatever the type of "value"; for the 2 "value" checkers
the types used to check are different ({{double[]}} vs {{Double}}).
The idea was certainly not to bypass the Java strong type-checking system: Having the {{Object}}
type in the "value" part of the {{Pair}} (in "SimplePointChecker") is because it is _not_

The proposal will make it clearer which type is the "point" and which is the "value" because
it will be explicit (through the instantiation of the generic type arguments).
> Naming confusion
> ----------------
>                 Key: MATH-707
>                 URL:
>             Project: Commons Math
>          Issue Type: Task
>            Reporter: Gilles
>            Assignee: Gilles
>            Priority: Trivial
>              Labels: api-change
>             Fix For: 3.0
> This issue was raised in [this thread|] on
the "dev" ML.
> It proposes to consistently name classes/interfaces that refer to number types (e.g.
"Real", "Complex", ...) and structure (e.g. "Scalar", "Vectorial", ...), with "Real" and "Scalar"
components in names being assumed (thus, not to be included in the name).
> For example, for the "Univariate..." interfaces (in package "analysis"), the proposal
is to operate the following renaming:
> * {{UnivariateRealFunction}} -> {{UnivariateFunction}}
> * {{UnivariateRealVectorialFunction}} -> {{UnivariateVectorFunction}}
> * {{UnivariateMatrixFunction}} -> {{UnivariateMatrixFunction}}
> Similar changes are in order in the package "optimization" (where "Real" is sometimes
included in the name and sometimes not, or used instead of "Scalar").

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message