diff options
author | dgp <dgp@users.sourceforge.net> | 2019-05-11 12:57:35 (GMT) |
---|---|---|
committer | dgp <dgp@users.sourceforge.net> | 2019-05-11 12:57:35 (GMT) |
commit | 923a6774f62e32298b5e46435e6a648e4ff1f53a (patch) | |
tree | 78ca86b6621bfbfbd66246c1f1e5597fdc51d9b0 | |
parent | 0d1ffc0968e6c82da985d876f63a92a1159a9a3b (diff) | |
parent | 9ca29b09ae01c2710010821b09fff5f613c7c26f (diff) | |
download | tcl-923a6774f62e32298b5e46435e6a648e4ff1f53a.zip tcl-923a6774f62e32298b5e46435e6a648e4ff1f53a.tar.gz tcl-923a6774f62e32298b5e46435e6a648e4ff1f53a.tar.bz2 |
merge 8.6
-rw-r--r-- | doc/TraceVar.3 | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/TraceVar.3 b/doc/TraceVar.3 index 19cb467..c3edfa4 100644 --- a/doc/TraceVar.3 +++ b/doc/TraceVar.3 @@ -331,11 +331,11 @@ trace procedures will always be invoked. .SH "RESTRICTIONS" .PP A trace procedure can be called at any time, even when there -is a partially formed result in the interpreter's result area. If +are partially formed results stored in the interpreter. If the trace procedure does anything that could damage this result (such -as calling \fBTcl_Eval\fR) then it must save the original values of -the interpreter's \fBresult\fR and \fBfreeProc\fR fields and restore -them before it returns. +as calling \fBTcl_Eval\fR) then it must use the \fBTcl_SaveInterpState\fR +and related routines to save and restore the original state of +the interpreter before it returns. .SH "UNDEFINED VARIABLES" .PP It is legal to set a trace on an undefined variable. |