On Mon, Oct 26, 2009 at 3:16 PM, Eskil Abrahamsen Blomfeldt <[email protected]> wrote: > Francis Galiegue skrev: >> >> There's a lot of @Override annotation keywords in the existing Java >> source, and the generator generates @Override annotations in the Java >> source code. >> >> But the target attribute of <javac> tasks were always 1.5... >> >> Which platforms running Qt Jambi still use 1.5? Why isn't 1.6 required >> all the way? >> >> > > I don't see any reason of scrapping compatibility with Java 1.5 at this > point. It's a convenience for people to be able to deploy to platforms which > do not necessarily have support for features introduced in new versions of > Java. When we initially introduced the dependency on Java 1.5, it was not a > decision taken lightly, but Java 1.5 was a quantum leap in terms of version > updates, and has so many handy features (generics, varargs, enums, > annotations to name a few) that we felt they outweighed any inconvenience > caused by the fact that we standardized on 1.5 at a time when 1.4 was the > most widely used version of Java. As far as I know, the same cannot be said > for Java 1.6. > > So the question is: Why would you want to introduce a new dependency? And > how does it relate to the Override-annotations? >
Well, I though at first that @Override appeared in 1.6, but having searched a little more thoroughly, it appears that I am mistaken: it appeared in 1.5. Forget my question... -- Francis Galiegue, [email protected] "It seems obvious [...] that at least some 'business intelligence' tools invest so much intelligence on the business side that they have nothing left for generating SQL queries" (Stéphane Faroult, in "The Art of SQL", ISBN 0-596-00894-5) _______________________________________________ Qt-jambi-interest mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-jambi-interest
