On Fri, Jun 20, 2014 at 9:00 PM, Gilles <[email protected]> wrote: > On Fri, 20 Jun 2014 16:57:41 +0200, Thomas Neidhart wrote: >> >> On 20 Jun 2014 16:37, "Gilles" <[email protected]> wrote: >>> >>> >>> On Fri, 20 Jun 2014 16:18:08 +0200, Thomas Neidhart wrote: >>>> >>>> >>>> Java 5 is already eol. Anybody still using it is certainly in >>>> maintenance >>>> mode thus adding now a feature that is available in java 6 does not make >>>> any sense. >>> >>> >>> >>> This a strong statement in a forum where it has _always_ been >>> indicated that no post-Java-5 feature could be used. >> >> >> These two are completely different things. >> >> Not using more recent java features was done in order to still support >> users that are stuck with java 5 but want/have to use commons. >> >> Duplicating java 6 features in 2014 is pointless. What is the expected >> userbase of this feature? > > > Commons Math itself. And this was the real purpose of duplicating Java 6: > no user ever asked for those methods in MathArrays. They were implemented > for the sole reason that CM could not contain calls to methods not yet > available in Java 5. [See the "pom.xml" of Commons Math.] > >> New users will certainly have adopted more recent >> versions of java and anybody still using java 5 and having a need for this >> will hopefully have implemented it already in his own codebase. > > > This is completely unrelated to the issue. > >>> >>> The right question, to be asked again (in case the answer will be >>> different from all the other times) is: Is Commons Math still to >>> support Java 5 ? >>> >>> If not, to which version do we switch to? 6, 7, 8?
I think JDK 7 may be the way to go ; since per http://www.oracle.com/technetwork/java/eol-135779.html ; even JDK 6 has stopped public updates since last year. >> >> >> Thats another question to be asked, but orthogonal to the above. > > > No. The question is really: In Commons Math, can we call JDK's features > that are post-Java-5? > The answer has up to now been "No". > > If it becomes "yes", there are several CM methods that can be deprecated, > and whose implementation can be right-away delegated to their JDK equivalent > (in particular the "copyOf" family in "MathArrays"). > > If it is still "No", for the reason you gave yourself above (users stuck > with > Java 5), then how is "copyOfRange" any different from all the other methods > with a similar purpose (which is: prepare for switching to higher Java > version)? > > > Gilles > > > --------------------------------------------------------------------- > 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]
