> Well, thread support was just added recently so before that
> having two interps in the same thread was the only way
> you could create two interps, cause there was only one thread.
>
> Besides that, it is nice to be able to have a child interp
> to run things in. It provides the ability to run safe interps
> and that sort of thing. For example, in Source-Navigator we
> use a child interp for each project file. Each project
> has its own copies of global Tcl variable and commands.
In aolserver one probably wouldn't need to do these types of things, but who
knows? Since aolserver provides its own api for registering thread exit and
cleanup procs, I could also use those. I'm guessing that they might have
disabled the tcl-specific calls in favor of the aolserver api functions. For
now, I can live with one interpreter per thread, but I can't live with the memory
leaks, so I'm going to pursue that. When I get the memory leaks taken care of,
I'll come back to this thread cleanup issue.
-Dan
----------------------------------------------------------------
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
