On Tue, 8 Aug 2000, Jiang Wu wrote:
> Darn! With problems like this, does it mean that there is no safe way of
> using a non-threaded Tcl in a JVM because the JVM is threaded by default.
> The JVM is going to allocate one thread to execute non-threaded Tcl code.
> Tcl tries to access system globals. JVM also tries to access the same
> system globals.
That does seem like a problem. If we require "special hacks" on
Tcl itself, then there is no point in trying to support a
pre-compiled version of Tcl Blend that gets loaded into Tcl.
Users will just have to download and build a threaded version
of Tcl or use our special hacks. A "core patch" seems like
a bad idea if you ask me.
It sure would make life easier if we just required Tcl
threads to use Tcl Blend. The notifier thing would go
away because we could count on threads being there.
Mo DeJong
Red Hat Inc
----------------------------------------------------------------
The TclJava mailing list is sponsored by Scriptics Corporation.
To subscribe: send mail to [EMAIL PROTECTED]
with the word SUBSCRIBE as the subject.
To unsubscribe: send mail to [EMAIL PROTECTED]
with the word UNSUBSCRIBE as the subject.
To send to the list, send email to '[EMAIL PROTECTED]'.
An archive is available at http://www.mail-archive.com/tcljava@scriptics.com
