From a user perspective, Jikes RVM uses classpath out of the box. (It
builds with unmodified GNU classpath releases and classpath cvs head; we
don't distribute GNU classpath with Jikes RVM).
We do provide our own versions of a few classes in java.* that the build
process selects instead of
Gah. :(
So if I am to understand this correctly: Classpath java.lang.* implementation does not rely on specifics of
any given VM* interface implementation, but said VM* interface implementations MAY rely on internals of
existing Classpath java.lang.* classes? (so there is a one-way dependency
On Mon, 2005-06-06 at 10:01 -0400, Aaron Hamid wrote:
Gah. :(
So if I am to understand this correctly: Classpath java.lang.* implementation
does not rely on specifics of any given VM* interface implementation, but said
VM* interface implementations MAY rely on internals of existing
[Original Message]
From: Sven de Marothy [EMAIL PROTECTED]
To: harmony-dev@incubator.apache.org
Date: 6/4/05 3:49:37 PM
Subject: Re: [arch] How much of java.* and friends does Harmony need
towrite. Was: VM/Classlibrary interface
On Sat, 2005-06-04 at 21:44 +0200, Santiago Gala wrote:
El dom, 05-06-2005 a las 01:56 -0500, Dan Lydick escribi:
(...)
I suppose I need to do some more homework then.
If GNU Classpath is used without modification for
numerous VM's, then great! Ultimately, what I am
A few classes need to be modified:
- jamvm (from README): A number of classes
