jyapayne/Nim
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix #7304 by clarifying integer width in manual (#7319)

Browse source 
* Fix #7304 by clarifying integer width in manual

* Update lexing.txt
This commit is contained in:
twetzel59 2018-03-17 15:25:28 -04:00 • committed by Andreas Rumpf
commit d20729e840
1 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/manual/lexing.txt
View file

@ -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 There exists a literal for each numerical type that is
defined. The suffix starting with an apostrophe ('\'') is called a 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 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 is optional if it is not ambiguous (only hexadecimal floating point literals
with a type suffix can be ambiguous). with a type suffix can be ambiguous).