# HG changeset patch
# User Chong Yidong <cyd@stupidchicken.com>
# Date 1267907239 18000
# Node ID 6773fa37732a6a9822b2053c6687b993d771c51f
# Parent  d4567b4f2db3bec1133c03a3f19b3aa124bba31b
* objects.texi (Integer Type): Take note of the read syntax exception for numbers that cannot fit in the integer type.

diff -r d4567b4f2db3 -r 6773fa37732a doc/lispref/ChangeLog
--- a/doc/lispref/ChangeLog	Sat Mar 06 14:02:49 2010 -0500
+++ b/doc/lispref/ChangeLog	Sat Mar 06 15:27:19 2010 -0500
@@ -1,3 +1,8 @@
+2010-03-06  Chong Yidong  <cyd@stupidchicken.com>
+
+	* objects.texi (Integer Type): Take note of the read syntax
+	exception for numbers that cannot fit in the integer type.
+
 2010-03-03  Glenn Morris  <rgm@gnu.org>
 
 	* numbers.texi (Integer Basics, Bitwise Operations):
diff -r d4567b4f2db3 -r 6773fa37732a doc/lispref/objects.texi
--- a/doc/lispref/objects.texi	Sat Mar 06 14:02:49 2010 -0500
+++ b/doc/lispref/objects.texi	Sat Mar 06 15:27:19 2010 -0500
@@ -200,6 +200,13 @@
 @end group
 @end example
 
+@noindent
+As a special exception, if a sequence of digits specifies an integer
+too large or too small to be a valid integer object, the Lisp reader
+reads it as a floating-point number (@pxref{Floating Point Type}).
+For instance, on most machines @code{536870912} is read as the
+floating-point number @code{536870912.0}.
+
   @xref{Numbers}, for more information.
 
 @node Floating Point Type