On Thu, 2004-07-01 at 22:34, David Holmes wrote: > > Andrew John Hughes wrote: > > If we don't have some 1.5 support, we risk the problem of not being able > > to compile Java applications that use the new language features of 1.5, > > because the support in these basic classes is missing. > > The new language features generally require additional class libraries, > modifications to existing classes, additional information in the classfile > or some combination of all three. In principle you could back-port some > things (like Enum support) to 1.4 VM's - but they tend to interact with > other new features. All-in-all I think you'd have to go for an all-out > effort to support all of the classes needed for the new language features. > It would be difficult to try and integrate them in isolation. > > David Holmes > > > > > _______________________________________________ > Classpath mailing list > [EMAIL PROTECTED] > http://lists.gnu.org/mailman/listinfo/classpath
That's why I think the best way is to approach this is via a branch, as previously mentioned, rather than on the main Classpath source. A few class libraries can make the leap (those that are mainly extensions to existing stuff), but most will be on the branch only until there is sufficient support. Of course, first we need a Free compiler and JVM for generics, enums, etc. Has anyone run the JDK 1.5 beta against Classpath using japitools? I know its not production but it may be interesting to see what the differences are. The licensing is different on the beta, so I'm wary about trying this myself. -- Andrew :-) Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html Value your freedom, or you will lose it, teaches history. `Don't bother us with politics' respond those who don't want to learn.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/classpath
