Integer literal

In computer science, an integer literal is a kind of literal for an integer whose value is directly represented in source code. For example, in the assignment statement, the string   is an integer literal indicating the value 1, while in the statement   the string   is an integer literal indicating the value 16, which is represented by   in hexadecimal (indicated by the   prefix).

By contrast, in, the expression   evaluates to 1 (as the cosine of 0), but the value 1 is not literally included in the source code. More simply, in  the expression   evaluates to 4, but the value 4 is not literally included. Further, in  the   is a string literal, not an integer literal, because it is in quotes. The value of the string is, which happens to be an integer string, but this is semantic analysis of the string literal – at the syntactic level   is simply a string, no different from.

Parsing
Recognizing a string (sequence of characters in the source code) as an integer literal is part of the lexical analysis (lexing) phase, while evaluating the literal to its value is part of the semantic analysis phase. Within the lexer and phrase grammar, the token class is often denoted, with the lowercase indicating a lexical-level token class, as opposed to phrase-level production rule (such as  ). Once a string has been lexed (tokenized) as an integer literal, its value cannot be determined syntactically (it is just an integer), and evaluation of its value becomes a semantic question.

Integer literals are generally lexed with regular expressions, as in Python.

Evaluation
As with other literals, integer literals are generally evaluated at compile time, as part of the semantic analysis phase. In some cases this semantic analysis is done in the lexer, immediately on recognition of an integer literal, while in other cases this is deferred until the parsing stage, or until after the parse tree has been completely constructed. For example, on recognizing the string  the lexer could immediately evaluate this to 16 and store that (a token of type   and value 16), or defer evaluation and instead record a token of type   and value.

Once literals have been evaluated, further semantic analysis in the form of constant folding is possible, meaning that literal expressions involving literal values can be evaluated at the compile phase. For example, in the statement  after the literals have been evaluated and the expression   has been parsed, it can then be evaluated to 4, though the value 4 does not itself appear as a literal.

Affixes
Integer literals frequently have prefixes indicating base, and less frequently suffixes indicating type. For example, in C++  indicates the value 16 (because hexadecimal) as an unsigned long long integer.

Common prefixes include: Common suffixes include:
 * or  for hexadecimal (base 16);
 * ,  or   for octal (base 8);
 * or  for binary (base 2).
 * or  for long integer;
 * or  for long long integer;
 * or  for unsigned integer.

These affixes are somewhat similar to sigils, though sigils attach to identifiers (names), not literals.

Digit separators
In some languages, integer literals may contain digit separators to allow digit grouping into more legible forms. If this is available, it can usually be done for floating point literals as well. This is particularly useful for bit fields and makes it easier to see the size of large numbers (such as a million) at a glance by subitizing rather than counting digits. It is also useful for numbers that are typically grouped, such as credit card number or social security numbers. Very long numbers can be further grouped by doubling up separators.

Typically decimal numbers (base-10) are grouped in three digit groups (representing one of 1000 possible values), binary numbers (base-2) in four digit groups (one nibble, representing one of 16 possible values), and hexadecimal numbers (base-16) in two digit groups (each digit is one nibble, so two digits are one byte, representing one of 256 possible values). Numbers from other systems (such as id numbers) are grouped following whatever convention is in use.

Examples
In Ada, C# (from version 7.0), D, Eiffel, Go (from version 1.13), Haskell (from GHC version 8.6.1), Java (from version 7), Julia, Perl, Python (from version 3.6), Ruby, Rust and Swift, integer literals and float literals can be separated with an underscore. There can be some restrictions on placement; for example, in Java they cannot appear at the start or end of the literal, nor next to a decimal point. While the period, comma, and (thin) spaces are used in normal writing for digit separation, these conflict with their existing use in programming languages as radix point, list separator (and in C/C++, the comma operator), and token separator.

Examples include:

In C++14 (2014) and the next version of C, C23, the apostrophe character may be used to separate digits arbitrarily in numeric literals. The underscore was initially proposed, with an initial proposal in 1993, and again for C++11, following other languages. However, this caused conflict with user-defined literals, so the apostrophe was proposed instead, as an "upper comma" (which is used in some other contexts).