will be
OK with requiring threaded Tcl with TclBlend.
-- Jiang Wu
[EMAIL PROTECTED]
-Original Message-
From: Mo DeJong [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 17, 2000 2:25 PM
To: Scott Redman
Cc: Jiang Wu; [EMAIL PROTECTED]
Subject: [Tcl Java] Re: [Tcl Java] RE: [Tcl Java] RE: [Tcl Ja
To: 'Mo DeJong'; Scott Redman
Cc: Jiang Wu; [EMAIL PROTECTED]
Subject: RE: [Tcl Java] Re: [Tcl Java] RE: [Tcl Java] RE: [Tcl Java]
Thread question in TclBlend
Will the C based Tcl extensions work the same with the threaded version of
Tcl versus the non-threaded Tcl? One reason for using
-- Scott
-Original Message-
From: Jiang Wu [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 16, 2000 11:59 AM
To: 'Scott Redman'
Cc: [EMAIL PROTECTED]
Subject: RE: [Tcl Java] RE: [Tcl Java] Thread question in TclBlend
In theory, JAVA_LOCK sounds like the right t
---
From: Scott Redman [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 15, 2000 6:45 PM
To: [EMAIL PROTECTED]
Subject: [Tcl Java] RE: [Tcl Java] Thread question in TclBlend
I think Problem 2 isn't a problem for what we're trying to
do, but I think you're right that it's easy to fix.
The JAVA_LOCK
]
Subject: RE: [Tcl Java] RE: [Tcl Java] Thread question in TclBlend
In theory, JAVA_LOCK sounds like the right thing to do in protecting the
notifier of a non-thread enabled Tcl interpreter. However, the
JAVA_LOCK is
not released while the Tcl interpreter is idling. The result is that any
