> From: Mark Wielaard [mailto:[EMAIL PROTECTED]]
>
> Hi,
>
> On Mon, Jun 19, 2000 at 03:02:41PM -0600, John Keiser wrote:
> > All native methods in the VM interface (which includes Thread.java) are
> > implemented in Japhar (or the respective VM). It is important to change
> > Japhar to work with this change, however.
>
> Which could be a problem since I never got Japhar working with
> Classpath :(
I'll look into that when I have time ... time is short tonight, though. (If
someone else is looking into it, don't let this dissuade you, please :)
> But I quickly looked at the lib/libnative/java.lang/thread.c file
> in Japhar
> and it seemed to already expect to get a jclass in yield and not
> a jobject.
> (And it even ignores that argument.) So the change should be OK
> for Japhar.
>
Yay!
> The only other VM I am aware of that is trying to use the
> Classpath classes
> is SableVM, but I don't believe it already has hooks for the Classpath VM
> interface. Are there any other VMs?
>
Just GCJ. Any VM that wrote its Thread interface to work with the Java
standard should be fine. Since they're probably going to ignore the class
argument anyway, as Japhar did, it doesn't matter too much even if they're
wrong (for static methods like this anyway).
Thanks.
--John
