This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: SV: Adding another configuration feature to libjava forarm-elfmetal configurations
- From: Anthony Green <green at redhat dot com>
- To: Andrew Haley <aph at redhat dot com>
- Cc: Øyvind Harboe <oyvind dot harboe at zylin dot com>, java at gcc dot gnu dot org
- Date: 01 May 2003 09:17:10 -0700
- Subject: Re: SV: Adding another configuration feature to libjava forarm-elfmetal configurations
- References: <41D1051F31A2674C99E41CA28EE734980A1FDD@isp-ex2k.intellimade.net><1051727681.1401.642.camel@escape> <16049.12048.574795.325791@masala.cambridge.redhat.com>
On Thu, 2003-05-01 at 07:28, Andrew Haley wrote:
> Javasoft do, with Java "profiles". I can't imagine any reason why
> they can but we can't.
Exactly for this reason...
> > One reason the library is so big is because the core classes are so
> > "connected". ie. ClassLoader requires networking requires
> > internationalization etc (or something like that).
>
> That's true. Presumably, making a profile involves disconnecting some
> classes such as internationalization.
And ClassLoaders, Threads, floating-point, etc... these aren't things
you can easily toggle on and off with our current implementation. My
gut reaction is that these issues are best handled through a fork within
the libjava tree. It seems like there's very little activity these days
in the classes that would form the intersection, so the maintenance
burden should not be too cumbersome.
AG