Re: [Sablevm-developer] Obsoleting sablevm-classpath NOW!

[Steven A. <au...@wa...>]

Etienne:  Jikes RVM uses a stock classpath build.  All it does is copy 
Classpath's glibj.zip and the .so files over to its own local storage 
place.

We get away with this because we put our own classes earlier in the 
path than Classpath's.  So we always get our own implementation of 
VMRuntime, for instance, and never see Classpath's.  Ditto for all of 
the other VM* classes, I believe.

I'm not sure what improved level of working out-of-the-box you would 
want beyond that.  Perhaps I have misunderstood what you're suggesting?

--Steve Augart


Etienne Gagnon wrote:
> I definitely think that Classpath should work *out-of-the-box* with all
> normal[0] VMs; something like:
[...]
> This would work best with:
> 0- All VM-specific code moved to VM*.java classes.
> 1- VM*.java classes residing in the *normal* Classpath tree.
> 2- Using m4 to maintain real VM-specific code. [Many VM's
>    will probably share "native" method declarations, for example].
> 3- The /vm subtree could be either eliminated, or kept around for
>    unusual[1] VM's.
> 
> 
> [0] I mean VM's with a usual build process, such as kaffe, sablevm, etc.
> [1] I mean VM's with unusual build process, such as JikesRVM, etc.

-- 
Steven Augart

Jikes RVM, open source Research Virtual Machine:
http://oss.software.ibm.com/jikesrvm

Office: +1 914/784-6743
T.J. Watson Research Center, IBM