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 :(
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.
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?
Cheers,
Mark
> -----Original Message-----
> From: Mark Wielaard [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, June 18, 2000 7:05 AM
> To: [EMAIL PROTECTED]
> Subject: Thread.yield() is static
>
>
> Hi,
>
> I found a smaal bug in vm/reference/java/lang/Thread.java.
> The method yield() should have been static.
> So I have changed it to read: public static synchronized native void
> yield();
> But I am not sure if I should also fix any native methods.
> Or are the native methods only defined in the vm implementations that use
> Classpath?
>
> It would be nice to have a bug database. Is there one we could use?
> And is there a cvs commit mailinglist?
>
> Cheers,
>
> Mark
>
>
