Since int() doesn't truncate any more (TIP #514), adapt the documentation accordingly

3 files changed, 5 insertions, 5 deletions

diff --git a/doc/expr.n b/doc/expr.n
index dfa77af..72f914a 100644
--- a/doc/expr.n
+++ b/doc/expr.n
@@ -340,7 +340,7 @@ prior to 8.5, integer calculations were performed using one of the C types
 \fIlong int\fR or \fITcl_WideInt\fR, causing implicit range truncation
 in those calculations where values overflowed the range of those types.
 Any code that relied on these implicit truncations should instead call
-\fBint()\fR or \fBwide()\fR, which do truncate.
+\fBwide()\fR, which does truncate.
 .PP
 Internal floating-point computations are
 performed using the \fIdouble\fR C type.
diff --git a/doc/scan.n b/doc/scan.n
index 382abb8..2719986 100644
--- a/doc/scan.n
+++ b/doc/scan.n
@@ -76,9 +76,9 @@ case, in a position in the result list.
 The syntactically valid values for the size modifier are \fBh\fR, \fBL\fR,
 \fBl\fR, and \fBll\fR.  The \fBh\fR size modifier value is equivalent
 to the absence of a size modifier in the the conversion specifier.
-Either one indicates the integer range to be stored is limited to
-the same range produced by the \fBint()\fR function of the \fBexpr\fR
-command.  The \fBL\fR size modifier is equivalent to the \fBl\fR size
+Either one indicates the integer range to be stored is limited to the range
+determined by the value of the \fBwordSize\fR element of the \fBtcl_platform\fR
+array).  The \fBL\fR size modifier is equivalent to the \fBl\fR size
 modifier. Either one indicates the integer range to be stored is
 limited to the same range produced by the \fBwide()\fR function of
 the \fBexpr\fR command.  The \fBll\fR size modifier indicates that
diff --git a/tests/oo.test b/tests/oo.test
index bae93e7..0ac7f86 100644
--- a/tests/oo.test
+++ b/tests/oo.test
@@ -4649,7 +4649,7 @@ test oo-35.7.3 {Bug 7842f33a5c: destructor cascading in stereotypes} -setup {
 } -body {
     # In this case, sub-objects are deleted while the destructor is running and
     # the destroy is neat, so things work sanely. Error follows standard Tcl
-    # error flow route; bgerror is not used. 
+    # error flow route; bgerror is not used.
     bgerrorIntercept ::result {
 	set FH [RpcClient new]
 	$FH create_bug