On Tue, 25 Jul 2000, Mike Schwartz wrote:
> Hmm, I just realized that the issue is the Interp.eval code isn't thread
> safe, so it just needs to run in a single Java thread (not necessarily the
> Java main thread). So the code I suggested below won't work but you get the
> idea -- have the code sanity check the call and not silently allow someone
> to stumble on a known limitation in the code...
>
> thanks
> - Mike
It is not a "known limitation". The fact that most of the methods
in the interp class are not thread safe is by design. The thread
safe event queue is the way to go. I am open to suggestions as to
how we could help people to not make this mistake in the future.
I think better documentation is the best approach, but writing docs
is boring so folks do not seem to want to help with that.
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
