Kaffe is #2 priority on the list, mainly because of the
Japhar+Classpath's relationship to one another (started out as one project
and split into two for modularity reasons). The point you make is good and
valid, though.
This port is nearly done, and with the knowledge we gain from doing it,
Kaffe will take very little time. Japhar is definitely stable enough now to
support our classes, so I don't see a big problem here.
I like the idea of borrowing Kaffe's AWT (you didn't say it
specifically, but it makes the most sense), simply because no one has worked
on it here and theirs is very portable (my goal is to get this thing fully
working on all Japhar's platforms *and* all Kaffe's platforms, *including*
Windows and DOS. Modifications would need to be made so that it doesn't use
Sun's private/protected field names anymore (I have a real problem with
that, and Sun might be able to make a fuss too).
Ideally, when we achieve portability with Kaffe, they would fold
Classpath in completely and take the best parts of both, and then both
Kaffe's class library developers and Classpath's would work on the class
library together, un-splintering the community's resources.
Then again, it might simply not happen that way if either of us get too
attached to our code. I sincerely hope that does not happen. I have no
desire to see a fight.
--John Keiser
> -----Original Message-----
> From: Artur Biesiadowski [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, October 21, 1998 3:15 AM
> To: [EMAIL PROTECTED]
> Subject: Kaffe as main target ?
>
>
> Classpath seems to focus on japhar as main release/testing platform. I
> understand that japhar needs core library, but I don't think that it is
> best place to test it. Maybe kaffe could be used instead ? It is a lot
> more stable, faster, has free java library that can be used to fill gaps
> (in other case we need to fill gaps with JDK classlib). Did anybody make
> a move in that direction ?
>
> Artur
>
>
>
