I would initially agree, but Math is still in early development (our
second minor release). I really doubt anyone has created any alternate
implementations of these interfaces that are in any production env. I
think Math is for the time being an implementation, not a standard. If
others were implementing any of our API's I think we would have found
out by now. I don't think we can guarantee that these apis will not
change over time, there is no "Standard" agreed upon for them outside of
Commons Math, there was no committee that said, this is what the "Math
API" will look like as in the way something like JAXP has arisen...
So I'll ask again, when is the appropriate time to add methods to an
interface? Seems your suggesting "never". I disagree, I believe that in
our case these modifications can be made and the result will be a major
version release, so I would say these changes go into 2.0, if we don't
want them in 1.1 then role them back temporarily for the release, or
better yet, tag the release in the cvs and move the tag on the
appropriate files prior to this change.
Finally, I think that a defining both the Interface and a Implementation
"stub", having third parties implement the stub to implement/extend the
API gives us the power to do such changes on minor revisions without
"breaking" anyones build in the future.
-Mark
Stephen Colebourne wrote:
Were I a voting member of [math] I would -1 such an incompatible
change to an interface. Interfaces need to be considered sacrosanct
and unchangable, no matter how painful that is. This is particularly
important in a high profile project like commons, where errors cause
serious implications to users.
We have got this wrong before:
- lang 2.0 deliberately changed the semantics of isEmpty. At least
major OSS user stopped using the library as a result.
- collections 3.0 accidentally changed IteratorUtils.EMPTY_ITERATOR.
Many OSS users still have a bad view of collections as a result.
Although the causes were different, the effect was the same. Thats why
we should be running a tool like clirr for each commons release. As,
I've said before, commons needs to strive to be whiter than white.
Lets not to get it wrong again when we have found the issue.
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]