summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorjan.nijtmans <nijtmans@users.sourceforge.net>2023-06-21 07:13:48 (GMT)
committerjan.nijtmans <nijtmans@users.sourceforge.net>2023-06-21 07:13:48 (GMT)
commit09c0f6835523794621c9bae88e5ea3b955c14878 (patch)
tree346e19c129eb5d40a77ac2febe99a9abccd086cc /doc
parent104527a10755e3d38008d55cc79bd8f76ce4d9e8 (diff)
downloadtcl-09c0f6835523794621c9bae88e5ea3b955c14878.zip
tcl-09c0f6835523794621c9bae88e5ea3b955c14878.tar.gz
tcl-09c0f6835523794621c9bae88e5ea3b955c14878.tar.bz2
"trace variable" -> "trace add variable" in testcases (and documentation)
Diffstat (limited to 'doc')
-rw-r--r--doc/trace.n2
-rw-r--r--doc/upvar.n2
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/trace.n b/doc/trace.n
index 570b263..9b8fd57 100644
--- a/doc/trace.n
+++ b/doc/trace.n
@@ -238,7 +238,7 @@ if an entire array is being deleted and the trace was registered
on the overall array, rather than a single element, then \fIname1\fR
gives the array name and \fIname2\fR is an empty string.
\fIName1\fR and \fIname2\fR are not necessarily the same as the
-name used in the \fBtrace variable\fR command: the \fBupvar\fR
+name used in the \fBtrace add variable\fR command: the \fBupvar\fR
command allows a procedure to reference a variable under a
different name.
\fIOp\fR indicates what operation is being performed on the
diff --git a/doc/upvar.n b/doc/upvar.n
index 91defe6..5d697dd 100644
--- a/doc/upvar.n
+++ b/doc/upvar.n
@@ -94,7 +94,7 @@ proc \fIsetByUpvar\fR { name value } {
set localVar $value
}
set originalVar 1
-trace variable originalVar w \fItraceproc\fR
+trace add variable originalVar write \fItraceproc\fR
\fIsetByUpvar\fR originalVar 2
.CE
.PP