From 95d2a7f7c08f468c9d9dbfed451dd3bad2a37129 Mon Sep 17 00:00:00 2001 From: dgp Date: Sat, 11 May 2019 12:48:53 +0000 Subject: Revised documented advice that made obsolete reference to interp->result. --- doc/TraceVar.3 | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/TraceVar.3 b/doc/TraceVar.3 index 97af6d4..caafcf1 100644 --- a/doc/TraceVar.3 +++ b/doc/TraceVar.3 @@ -329,11 +329,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. -- cgit v0.12