Hello everyone, In the recent changes for 3.0, the solvers now have a setting for a maximal number of function evaluations rather than a max number of iterations. This number cannot be specified at construction time, but only using a setMaxEvaluations() method declared in the BaseUnivariateRealSolver interface.
Wouldn't it be wise to allow this setting ? Also one of my coworkers was trapped by the changed signatures. Since there is no constructor with one integer and one double, an existing code that used the 2.X versions did provide the number of iterations and the absolute tolerance. As integers are automatically promoted to double when needed, his code was in fact calling a new constructor with two doubles, and the first argument was considered to be a relative tolerance ... Do you think we could set up some compliance constructors that would consider the maxIterations as a maxEvaluation (as these are mainly safeguard, it should be OK for many people) and provide a default relative tolerance ? Luc --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
