diff options
author | hobbs <hobbs> | 2006-11-03 00:34:51 (GMT) |
---|---|---|
committer | hobbs <hobbs> | 2006-11-03 00:34:51 (GMT) |
commit | c399e676c8dbdec3ce1fe4b694d7c269f9b1f675 (patch) | |
tree | 13086bc5f8998596d202f1bdeaa9df4ed46bc3cd /doc/eval.n | |
parent | ee75480f2f9483654c8f665acd984569f3234ca8 (diff) | |
download | tcl-c399e676c8dbdec3ce1fe4b694d7c269f9b1f675.zip tcl-c399e676c8dbdec3ce1fe4b694d7c269f9b1f675.tar.gz tcl-c399e676c8dbdec3ce1fe4b694d7c269f9b1f675.tar.bz2 |
* doc/ParseCmd.3, doc/Tcl.n, doc/eval.n, doc/exec.n:
* doc/fconfigure.n, doc/interp.n, doc/unknown.n:
* library/auto.tcl, library/init.tcl, library/package.tcl:
* library/safe.tcl, library/tm.tcl, library/msgcat/msgcat.tcl:
* tests/all.tcl, tests/basic.test, tests/cmdInfo.test:
* tests/compile.test, tests/encoding.test, tests/execute.test:
* tests/fCmd.test, tests/http.test, tests/init.test:
* tests/interp.test, tests/io.test, tests/ioUtil.test:
* tests/iogt.test, tests/namespace-old.test, tests/namespace.test:
* tests/parse.test, tests/pkg.test, tests/pkgMkIndex.test:
* tests/proc.test, tests/reg.test, tests/trace.test:
* tests/upvar.test, tests/winConsole.test, tests/winFCmd.test:
* tools/tclZIC.tcl:
* generic/tclParse.c (Tcl_ParseCommand): Replace {expand} with {*}
officially (TIP #293). Leave -DALLOW_EXPAND=0|1 option to keep
{expand} syntax for transition users. [Bug 1589629]
Diffstat (limited to 'doc/eval.n')
-rw-r--r-- | doc/eval.n | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -5,7 +5,7 @@ '\" See the file "license.terms" for information on usage and redistribution '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES. '\" -'\" RCS: @(#) $Id: eval.n,v 1.6 2004/10/27 09:36:58 dkf Exp $ +'\" RCS: @(#) $Id: eval.n,v 1.7 2006/11/03 00:34:51 hobbs Exp $ '\" .so man.macros .TH eval n "" Tcl "Tcl Built-In Commands" @@ -53,7 +53,7 @@ for {set i 0} {$i<10} {incr i} { .VS 8.5 Note that in the most common case (where the script fragment is actually just a list of words forming a command prefix), it is better -to use \fB{expand}$script\fR when doing this sort of invokation +to use \fB{*}$script\fR when doing this sort of invokation pattern. It is less general than the \fBeval\fR command, and hence easier to make robust in practice. .VE 8.5 @@ -73,7 +73,7 @@ proc lprepend {varName args} { However, the last line would now normally be written without \fBeval\fR, like this: .CS -set var [linsert $var 0 {expand}$args] +set var [linsert $var 0 {*}$args] .CE .VE 8.5 |