----- Original Message ----- > On Oct 15, 2012, at 2:37 AM, Pekka Enberg <penb...@kernel.org> wrote: > > > On Sat, 13 Oct 2012, Ivan Maidanski wrote: > >> If you could show the community that upgrading to 1.7 brings some > >> benefit (e.g., like above) then it is ok to upgrade to 1.7 > >> directly > >> (thus eliminating Classpath VM implementors efforts to verify with > >> 1.6). > > > > Java 1.7 has some nice language changes: > > > > http://docs.oracle.com/javase/7/docs/technotes/guides/language/enhancements.html#javase7 > > > > and more importantly, invokedynamic, that's heavily used by > > upcoming JRuby > > 1.7. IIRC, Scala 2.10 will no longer run on Java 1.5 either. > > > > Pekka > > Although jruby needs invokedynamic to perform better I don't think > this means the class library needs to change source version unless an > actual API change would be unrecognized otherwise? You do however > need > a vm that supports invokedynamic and uses GNU Classpath. Does one > exist? >
This is sort of the point I was making, indirectly. 1.7 bytecode doesn't help anything until it's supported by VMs and it'll only be used (I imagine) in java.lang.invoke, which we don't have yet. It would be interesting to get HotSpot working with GNU Classpath... hahaha! > -- Andrew :) Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: 248BDC07 (https://keys.indymedia.org/) Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07
