I believe that once we port to Kaffe we will see cooperation on the class
libraries.
I am curious, though, what specifically have we done better? The only thing
I can think of is that our stuff has more doc comments ... and we have 1.2
java.util.
I do suggest that whoever works on AWT look at their implementation at
least; it would be really nice to have Classpath work on multiple platforms
by default. This is Java, after all, even if we can't use the name.
--John Keiser
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Paul Fisher
> Sent: Wednesday, October 21, 1998 9:57 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Kaffe as main target ?
>
>
> Artur Biesiadowski <[EMAIL PROTECTED]> writes:
>
> > 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).
>
> One of the great benefits of using Japhar is that we're making it more
> stable. Unlike using Sun's classes.zip, when we find a bug, we can
> easily track down the part of Japhar that's broken and implement a fix
> (or just bug toshok to fix it). The fact that Japhar is slower than
> Kaffe is a non-issue. Japhar does work.
>
> We plan to eventually support Kaffe, but I don't see a need to make
> that our primary testing/release platform. Transvirtual has been
> generally uncooperative regarding overlap of work between their class
> libraries and ours. Except for the AWT, we have much more
> functionality that their class libraries.
>
> --
> Paul Fisher * [EMAIL PROTECTED]
>
>
