summaryrefslogtreecommitdiffstats
path: root/win
diff options
context:
space:
mode:
authordgp <dgp@users.sourceforge.net>2009-06-13 14:38:44 (GMT)
committerdgp <dgp@users.sourceforge.net>2009-06-13 14:38:44 (GMT)
commit75857eb1811ac33b4d22fe4dc0949b9975a005a8 (patch)
treeba2f380d72e881d52e3720c24fccf6aad4eb80c3 /win
parent04ea78ea6abac1b67cda877f32c8a79a0496b44b (diff)
downloadtcl-75857eb1811ac33b4d22fe4dc0949b9975a005a8.zip
tcl-75857eb1811ac33b4d22fe4dc0949b9975a005a8.tar.gz
tcl-75857eb1811ac33b4d22fe4dc0949b9975a005a8.tar.bz2
* generic/tclCompile.c: The value stashed in iPtr->compiledProcPtr
* generic/tclProc.c: when compiling a proc survives too long. We * tests/execute.test: only need it there long enough for the right TclInitCompileEnv() call to re-stash it into envPtr->procPtr. Once that is done, the CompileEnv controls. If we let the value of iPtr->compiledProcPtr linger, though, then any other bytecode compile operation that takes place will also have its CompileEnv initialized with it, and that's not correct. The value is meant to control the compile of the proc body only, not other compile tasks that happen along. Thanks to Carlos Tasada for discovering and reporting the problem. [Bug 2802881].
Diffstat (limited to 'win')
0 files changed, 0 insertions, 0 deletions