* doc/AppInit.3:

	* doc/Async.3:
	* doc/BackgdErr.3:
	* doc/CrtChannel.3:
	* doc/CrtInterp.3:
	* doc/CrtMathFnc.3:
	* doc/DString.3:
	* doc/Eval.3:
	* doc/ExprLong.3:
	* doc/GetInt.3:
	* doc/GetOpnFl.3:
	* doc/Interp.3:
	* doc/LinkVar.3:
	* doc/OpenFileChnl.3:
	* doc/OpenTcp.3:
	* doc/PkgRequire.3:
	* doc/RecordEval.3:
	* doc/SetResult.3:
	* doc/SplitList.3:
	* doc/StaticPkg.3:
	* doc/TraceVar.3:
	* doc/Translate.3:
	* doc/UpVar.3:
	* doc/load.n: removed or updated references to interp->result use.

1 files changed, 13 insertions, 13 deletions

diff --git a/doc/Eval.3 b/doc/Eval.3
index de4540e..b395f75 100644
--- a/doc/Eval.3
+++ b/doc/Eval.3
@@ -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.3,v 1.5 1999/08/19 02:58:34 hobbs Exp $
+'\" RCS: @(#) $Id: Eval.3,v 1.6 2000/04/14 23:01:50 hobbs Exp $
 '\" 
 .so man.macros
 .TH Tcl_Eval 3 8.1 Tcl "Tcl Library Procedures"
@@ -108,18 +108,18 @@ of the words for the Tcl command, one word in each object in
 \fIobjv\fR.  \fBTcl_EvalObjv\fR evaluates the command and returns
 a completion code and result just like \fBTcl_EvalObjEx\fR.
 .PP
-\fBTcl_Eval\fR is similar to \fBTcl_EvalObjEx\fR except that
-the script to be executed is supplied as a string instead of an
-object and no compilation occurs.  The string is parsed and executed
-directly (using \fBTcl_EvalObjv\fR) instead of compiling it and
-executing the bytecodes.  In situations where it is known that the
-script will never be executed again, \fBTcl_Eval\fR may be
-faster than \fBTcl_EvalObjEx\fR.  \fBTcl_Eval\fR returns a completion
-code and result just like \fBTcl_EvalObjEx\fR.  Note: for backward
-compatibility with versions before Tcl 8.0, \fBTcl_Eval\fR
-copies the object result in \fIinterp\fR to \fIinterp->result\fR
-where it can be accessed directly.  This makes \fBTcl_Eval\fR somewhat
-slower than \fBTcl_EvalEx\fR, which doesn't do the copy.
+\fBTcl_Eval\fR is similar to \fBTcl_EvalObjEx\fR except that the script to
+be executed is supplied as a string instead of an object and no compilation
+occurs.  The string is parsed and executed directly (using
+\fBTcl_EvalObjv\fR) instead of compiling it and executing the bytecodes.
+In situations where it is known that the script will never be executed
+again, \fBTcl_Eval\fR may be faster than \fBTcl_EvalObjEx\fR.
+\fBTcl_Eval\fR returns a completion code and result just like
+\fBTcl_EvalObjEx\fR.  Note: for backward compatibility with versions before
+Tcl 8.0, \fBTcl_Eval\fR copies the object result in \fIinterp\fR to
+\fIinterp->result\fR (use is deprecated) where it can be accessed directly.
+This makes \fBTcl_Eval\fR somewhat slower than \fBTcl_EvalEx\fR, which
+doesn't do the copy.
 .PP
 \fBTcl_EvalEx\fR is an extended version of \fBTcl_Eval\fR that takes
 additional arguments \fInumBytes\fR and \fIflags\fR.  For the