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.

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index 2f693df8f988b248f9473715c61056ea134ca835..2422ee5cc0938fc89bdb8ea3c969661ab1fcb791 100644 (file)
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,3 +1,9 @@
+2014-01-05  Paul Eggert  <eggert@cs.ucla.edu>
+
+       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.
+
 2014-01-03  Chong Yidong  <cyd@gnu.org>
 
        * help.texi (Documentation, Accessing Documentation): Copyedits.

diff --git a/doc/lispref/strings.texi b/doc/lispref/strings.texi
index 5ae867549991ed8e43515612e3fa21ea0280c135..61e44fbafac88190e2850e966ffdd21b9039e87b 100644 (file)
--- 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")