From d20729e840af9c504ba6ca3726bf0e4ca8f47a99 Mon Sep 17 00:00:00 2001 From: twetzel59 Date: Sat, 17 Mar 2018 15:25:28 -0400 Subject: [PATCH] Fix #7304 by clarifying integer width in manual (#7319) * Fix #7304 by clarifying integer width in manual * Update lexing.txt --- doc/manual/lexing.txt | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/manual/lexing.txt b/doc/manual/lexing.txt index 915e879717..0328ffd55d 100644 --- a/doc/manual/lexing.txt +++ b/doc/manual/lexing.txt @@ -344,9 +344,11 @@ prefix), binary (prefix ``0b``), octal (prefix ``0o`` or ``0c``) and hexadecimal There exists a literal for each numerical type that is defined. The suffix starting with an apostrophe ('\'') is called a -`type suffix`:idx:. Literals without a type suffix are of the type ``int``, +`type suffix`:idx:. Literals without a type suffix are of an integer type, unless the literal contains a dot or ``E|e`` in which case it is of -type ``float``. For notational convenience the apostrophe of a type suffix +type ``float``. This integer type is ``int`` if the literal is in the range +``low(i32)..high(i32)``, otherwise it is ``int64``. +For notational convenience the apostrophe of a type suffix is optional if it is not ambiguous (only hexadecimal floating point literals with a type suffix can be ambiguous).