diff options
author | dgp <dgp@users.sourceforge.net> | 2009-06-13 14:25:12 (GMT) |
---|---|---|
committer | dgp <dgp@users.sourceforge.net> | 2009-06-13 14:25:12 (GMT) |
commit | 3f776aa9379874671930875ff55e00f3e7567644 (patch) | |
tree | e378dac3e887056d2ad1c01a857e14a546caa634 /unix | |
parent | 855a348eeae253e6765ea3edf689e41d79a7c081 (diff) | |
download | tcl-3f776aa9379874671930875ff55e00f3e7567644.zip tcl-3f776aa9379874671930875ff55e00f3e7567644.tar.gz tcl-3f776aa9379874671930875ff55e00f3e7567644.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 'unix')
0 files changed, 0 insertions, 0 deletions