Mark Diggory wrote:
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.
Why? How would we know? Users just download the jar, and implement away. They don't need to talk back to the list. By defining a 1.0 release [math] said 'this is complete' and 'these interfaces will not change'. If we were talking 0.6 to 0.7 here it wouldn't matter.

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,
Again, I stress this point. Commons has many interfaces that we would like to change after the fact (eg. MultiMap in [collections], or DynaProperty in [beanutils]). AFAIN, none have been changed even over a major release version (awaiting someone to prove me wrong...).

If this were code within a company, then it wouldn't matter. But this is a publicly available, fully released, API. Open source is sometimes a pain to work with. This is one of those occasions. And IMHO, all commons would suffer were the change to happen.

For the record (and in accordance with informing people at the earliest point possible), I will -1 a 1.x release that changes an interface. I will -0/-1 a 2.0 release that changes an interface depening on further discussion. (Bearing in mind that my vote is non-binding, as a non-math committer)

Stephen

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to