commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gilles Sadowski <>
Subject [Math] About MATH-768
Date Sun, 15 Jul 2012 02:21:41 GMT

Referring to:

It seems that cleanly fixing that issue would require to create several
new classes inside the "o.a.c.m.complex" package (like
"UnivariateComplexFunction", "PolynomialComplexFunction",
"BaseAbstractUnivariateSolver", etc.) all of which would mostly duplicate
code in existing classes that manipulate primitive "double"s (instead of
"Complex" objects).
I'm wary to undertake this duplication without a deeper analysis of what
would be a good design of utilities for "complex" analysis. [And when we
talk about that, the very first issue to resolve would be MATH-667
(representation of the complex numbers).]

Hence, in order to resolve MATH-768 for the time being, and though it is not
satifactory, I'd make the "solveAll" public again (but marked as deprecated,
without any better replacement for now).

Any objections? Better ideas?


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message