Re: TclX loop slow in the default case
- From: Alexandre Ferrieux <alexandre.ferrieux@xxxxxxxxx>
- Date: Fri, 29 Aug 2008 08:48:58 -0700 (PDT)
On Aug 29, 12:42 pm, miguel <mso...@xxxxxxxxxxxx> wrote:
Alexandre Ferrieux wrote:
Random idea: what about extending the bytecode compiler API so that it
can be passed a non-empty "context" (compiledLocals, possibly
literals, etc) instead of starting afresh ? This way, in the dominant
case where the upper context is also a compiled proc, the body-
bytecode would "land" among the upper locals and access them at full
speed (not even a linkvar). Or is such sharing of lists of compiled
locals impossible in the current setup ?
Done in 8.6 HEAD since 2008-06-08 [Patch 1973096]
Guys, what's nice with Miguel is that not only does he make my drems
come true, but sometimes he does it in advance just to be sure 8^P
.
- Follow-Ups:
- Re: TclX loop slow in the default case
- From: Uwe Klein
- Re: TclX loop slow in the default case
- References:
- TclX loop slow in the default case
- From: Evil Son
- Re: TclX loop slow in the default case
- From: Alexandre Ferrieux
- Re: TclX loop slow in the default case
- From: Evil Son
- Re: TclX loop slow in the default case
- From: Donal K. Fellows
- Re: TclX loop slow in the default case
- From: Alexandre Ferrieux
- Re: TclX loop slow in the default case
- From: Evil Son
- Re: TclX loop slow in the default case
- From: Alexandre Ferrieux
- Re: TclX loop slow in the default case
- From: Donal K. Fellows
- TclX loop slow in the default case
- Prev by Date: Re: Idea for new ttk Notebook virtual event
- Next by Date: Re: TclX loop slow in the default case
- Previous by thread: Re: [OT] random? (Re: TclX loop slow in the default case)
- Next by thread: Re: TclX loop slow in the default case
- Index(es):