[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


From: arenn
Subject: Re: JOS
Date: Sat, 25 Nov 2000 07:38:50 -0600

Brian Jones (address@hidden) wrote:
> The following article was interesting to me.  I don't know what the
> state of the JOS project is or who our liason is.  Could someone from
> that project bring us up to date with respect to this email referenced
> below?

It is interesting.  If I might extract their points:

1.  They think that replacement classes should be written in an alternate
namespace, then ported over when completed.  This certainly solves some
chicken and egg problems, but it creates new ones of its own.  I don't
object to that approach, but what we currently have seems to be working

2.  Classpath/libgcj merger.  No impact to JOS except that perhaps
JOS could be compiled at some point.

3.  VM specific aspects of Classpath.  Yes, we have them.  I don't see
any way around them.  And as noted, we do keep them separate from the
main tree.

This is what I gather after a very brief review.

Aaron M. Renn (address@hidden)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]