Re: Own implementation of multithread
- From: "Donal K. Fellows" <donal.k.fellows@xxxxxxxxxxxxxxxx>
- Date: Fri, 29 Aug 2008 11:06:34 +0100
Donald Arseneau wrote:
It is my understanding, and I am anxious to have any wrong
understandings corrected, that you don't even need to compile
Tcl with --enable-threads, which is only necessary if Tcl
manages the threads and communication between them.
That's wrong, because when Tcl's built unthreaded it uses some static
data allocation strategies (for things that are otherwise shared between
threads) that are deeply wrong when more than one thread is in use. When
built threaded, such additional locks as are required are added.
If you're using Tcl from multiple threads, you should use a
thread-enabled build. If you're wanting to do communication between
threads or scripted control of them, the Thread extension is commended
as providing the tools required. :-)
Donal.
.
- References:
- Own implementation of multithread
- From: lkfstephen
- Re: Own implementation of multithread
- From: Donald Arseneau
- Own implementation of multithread
- Prev by Date: Idea for new ttk Notebook virtual event
- Next by Date: Re: TclX loop slow in the default case
- Previous by thread: Re: Own implementation of multithread
- Next by thread: finding out tags in a specified area on the canvas widget identified by x,y
- Index(es):
Relevant Pages
|