> > OK. So there is indeed an incompatible change between 2.1 and current (to > > become 2.2). Is this really a problem? I mean, it could be seen as a bug > > fix (i.e. it was a mistake to return the super-class type)! > > Does the policy forbid such kind of fixes even if prevents the development > > of CM code that depends on these fixes? > > What exactly does postponing this change prevent? Why can't we just > cast the return if necessary? The class itself is deprecated, to be > removed I assume in 3.0, so I don't see much risk in our casting > return types internally in the interim. Am I missing something here?
No; I was. I thought that you were referring to a similar code in the "BicubicSplineInterpolator" class! The "SmoothingBicubicSplineInterpolator" can be reverted with no further thought. > [...] Sorry for the noise, Gilles --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
