summaryrefslogtreecommitdiff
path: root/lispref
diff options
context:
space:
mode:
authorEli Zaretskii <eliz@gnu.org>2001-09-08 17:41:41 +0000
committerEli Zaretskii <eliz@gnu.org>2001-09-08 17:41:41 +0000
commit3afd8c2506bbc99fc62c2363e4881319018e5a8a (patch)
tree2aadfb69fcb722bcc7a636e07351ae96fef6e21b /lispref
parent7cc80f0aefd4cbdd6fd0e827b67216c68e08b2ef (diff)
downloademacs-3afd8c2506bbc99fc62c2363e4881319018e5a8a.tar.gz
(String Conversion) <string-to-number>: Document
that a float is returned for integers that are too large.
Diffstat (limited to 'lispref')
-rw-r--r--lispref/strings.texi4
1 files changed, 3 insertions, 1 deletions
diff --git a/lispref/strings.texi b/lispref/strings.texi
index b80dc244ee0..f35f94b2bc4 100644
--- a/lispref/strings.texi
+++ b/lispref/strings.texi
@@ -536,7 +536,9 @@ This function returns the numeric value of the characters in
in that base. If @var{base} is @code{nil}, then base ten is used.
Floating point conversion always uses base ten; we have not implemented
other radices for floating point numbers, because that would be much
-more work and does not seem useful.
+more work and does not seem useful. If @var{string} looks like an
+integer but its value is too large to fit into a Lisp integer,
+@code{string-to-number} returns a floating point result.
The parsing skips spaces and tabs at the beginning of @var{string}, then
reads as much of @var{string} as it can interpret as a number. (On some