summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authordkf <donal.k.fellows@manchester.ac.uk>2019-05-17 07:31:47 (GMT)
committerdkf <donal.k.fellows@manchester.ac.uk>2019-05-17 07:31:47 (GMT)
commitc54b6957b8f0577a8d2789b9cc88a04a7da7a478 (patch)
treea88c9c80571094587464060f1a831a268d8e8302 /doc
parent0f34d49b76e87e5f454a9b468e981bc71f43907c (diff)
parent503da2614f2490195b2bd436c44cc52f3678becd (diff)
downloadtcl-c54b6957b8f0577a8d2789b9cc88a04a7da7a478.zip
tcl-c54b6957b8f0577a8d2789b9cc88a04a7da7a478.tar.gz
tcl-c54b6957b8f0577a8d2789b9cc88a04a7da7a478.tar.bz2
merge core-8-branch
Diffstat (limited to 'doc')
-rw-r--r--doc/TraceVar.38
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.