On Tue, 25 Jul 2000, Jiang Wu wrote:
> But I do agree that there needs to be better documentation or code to help
> with the correct usage of the model. What if we are to add a few helper
> methods such as:
>
> public static tcl.lang.Interp Interp.createInterp();
>
> which will create a thread, create an Interp to use the dedicated thread,
> start the event listener, and return the Interp.
Now there is an interesting idea. The fact that you need to create an
interp in the thread that it will live in is kind of a tricky detail
that we might want to shelter folks from.
> Or have something like this for people using TclBlend with non-threaded Tcl:
>
> public static tcl.lang.Interp Interp.getTheGlobalInterp();
>
> which checks to see if the global interpreter is created already. If it is,
> returns the global Interp object. If not, create the interpreter, assigns
> it a thread, starts the event listener, and returns the Interp.
I am not sure I like this one as much. The interp class should really
only contain APIs that work with both Jacl and Tcl Blend.
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
