Re: Own implementation of multithread
- From: Alexandre Ferrieux <alexandre.ferrieux@xxxxxxxxx>
- Date: Thu, 28 Aug 2008 00:43:21 -0700 (PDT)
On Aug 28, 12:15 am, lkfstep...@xxxxxxxxx wrote:
In c++ code, I am trying to create many threads, each thread will
create its own interpreter.
Each interpreter will need to eval a script.
...
I would like to ask is this approach is wrong?
It is hard to say without further details on your constraints, but
when possible it is better to stay at script level as pervasively as
possible, simply because for coarse-granularity operations like
spawning a thread+interp, there's no added value (like speed) in doing
it at the low level, while there's added complexity.
Maybe you can elaborate: is there an external requirement preventing
you from doing the "master" part in a Tcl script using the Thread
package ?
-Alex
.
- References:
- Own implementation of multithread
- From: lkfstephen
- Own implementation of multithread
- Prev by Date: Re: TclX loop slow in the default case
- Next by Date: Help me
- Previous by thread: Own implementation of multithread
- Next by thread: Re: Own implementation of multithread
- Index(es):
Relevant Pages
|