[MATH-707] Naming confusion

• Type: Task
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Fix Version/s: 3.0
• Labels: api-change
• Assignee: Gilles Sadowski
• Reporter: Gilles Sadowski
• Created: 16/Nov/11 16:30
• Updated: 24/Mar/12 16:16
• Resolved: 14/Feb/12 00:25

Description

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").