summaryrefslogtreecommitdiff
path: root/doc/lispref/strings.texi
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2014-01-04 17:24:41 -0800
committerPaul Eggert <eggert@cs.ucla.edu>2014-01-04 17:24:41 -0800
commit7c2127d0f4151164c47ab811c4c134922f7f9c44 (patch)
treedde6d9bc3411ece2ee6f855880635cb097d78127 /doc/lispref/strings.texi
parent54c2b8b4976995177f6fb375c2d52280f1d152d1 (diff)
downloademacs-7c2127d0f4151164c47ab811c4c134922f7f9c44.tar.gz
Document behavior of (string-to-number "+@") (Bug#16293).
* strings.texi (String Conversion): Document behavior of string-to-number on invalid strings that begin with "+", too.
Diffstat (limited to 'doc/lispref/strings.texi')
-rw-r--r--doc/lispref/strings.texi6
1 files changed, 2 insertions, 4 deletions
diff --git a/doc/lispref/strings.texi b/doc/lispref/strings.texi
index 5ae86754999..61e44fbafac 100644
--- a/doc/lispref/strings.texi
+++ b/doc/lispref/strings.texi
@@ -622,10 +622,8 @@ but its value is too large to fit into a Lisp integer,
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 in
the given base. (On some systems it ignores other whitespace at the
-beginning, not just spaces and tabs.) If the first character after
-the ignored whitespace is neither a digit in the given base, nor a
-plus or minus sign, nor the leading dot of a floating point number,
-this function returns 0.
+beginning, not just spaces and tabs.) If @var{string} cannot be
+interpreted as a number, this function returns 0.
@example
(string-to-number "256")