From: Gurusamy Sarathy <gsar@cpan.org>
Date: Fri, 26 Mar 1999 00:50:51 +0000 (+0000)
Subject: better description of "Integer overflow" diagnostic
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=a7ae9550f26a080556f67048e2697d3c5a20f9f4;p=p5sagit%2Fp5-mst-13.2.git

better description of "Integer overflow" diagnostic

p4raw-id: //depot/perl@3169
---

diff --git a/pod/perldiag.pod b/pod/perldiag.pod
index fb6d139..73a4693 100644
--- a/pod/perldiag.pod
+++ b/pod/perldiag.pod
@@ -1441,17 +1441,16 @@ C<$ENV{ENV}> or C<$ENV{BASH_ENV}> are derived from data supplied (or
 potentially supplied) by the user.  The script must set the path to a
 known value, using trustworthy data.  See L<perlsec>.
 
-=item Integer overflow in hex number
-
-(S) The literal hex number you have specified is too big for your
-architecture. On a 32-bit architecture the largest hex literal is
-0xFFFFFFFF.
-
-=item Integer overflow in octal number
-
-(S) The literal octal number you have specified is too big for your
-architecture. On a 32-bit architecture the largest octal literal is
-037777777777.
+=item Integer overflow in %s number
+
+(S) The literal hex, octal or binary number you have specified is
+too big for your architecture. On a 32-bit architecture the largest
+literal hex, octal or binary number representable without overflow
+is 0xFFFFFFFF, 037777777777, or 0b11111111111111111111111111111111
+respectively.  Note that Perl transparently promotes decimal literals
+to a floating point representation internally--subject to loss of
+precision errors in subsequent operations--so this limit usually
+doesn't apply to decimal literals.
 
 =item Internal inconsistency in tracking vforks