ue.
>
> This brings up a big question: can the notifier of a non-thread enabled Tcl
> interpreter be safely alerted by multiple threads.
>
> -- Jiang Wu
>[EMAIL PROTECTED]
>
> -Original Message-
> From: Mo DeJong [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 18, 2000
iginal Message-
From: Mo DeJong [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 18, 2000 4:16 PM
To: [EMAIL PROTECTED]
Subject: [Tcl Java] RE: [Tcl Java] Threa d question in TclBlend
Well, how do we prevent the Tcl event queue from being accessed
from multiple Java threads? In the case where Tcl
Well, how do we prevent the Tcl event queue from being accessed
from multiple Java threads? In the case where Tcl is threaded,
Tcl should do its own locking. In the case where Tcl
is not threaded, I would think we would need the JVM to do
the locking (AKA JAVA_LOCK). I am not convinced that we nee
mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 18, 2000 2:43 PM
To: [EMAIL PROTECTED]
Subject: [Tcl Java] RE: [Tcl Java] Re: [Tcl Java] RE: [Tcl Java] RE:
[Tcl Java] Threa d question in TclBlend
I thought the whole point you were making was that if we require that
Tcl be built with threads then we
I thought the whole point you were making was that if we require that
Tcl be built with threads then we could remove the JAVA_LOCK stuff.
How do you suggest we implement locking in a non thread enabled version
of Tcl if we are not going to use the current JAVA_LOCK approach?
Mo Dejong
Red Hat Inc
