Literals/Integer
From Rosetta Code
You are encouraged to solve this task according to the task description, using any language you may know.
Show how integer literals can be expressed in as many bases as your language allows.
Note: this should not involve the calling of any functions/methods but should be interpreted by the compiler or interpreter as an integer written to a given base.
Also show any other ways of expressing literals, e.g. for different types of integers.
[edit] Ada
In Ada integer literals may have the form <base>#<numeral>#. Here <base> can be from the range 2..16. For example:
with Ada.Integer_Text_IO; use Ada.Integer_Text_IO;
procedure Test_Literals is
begin
Put (16#2D7#);
Put (10#727#);
Put (8#1_327#);
Put (2#10_1101_0111#);
end Test_Literals;
Sample output:
727 727 727 727
[edit] ALGOL 68
Works with: ALGOL 68 version Revision 1 - no extensions to language used
Works with: ALGOL 68G version Any - tested with release 1.18.0-9h.tiny
Works with: ELLA ALGOL 68 version Any (with appropriate job cards) - tested with release 1.8-8d
Binary literals are of type BITS, and need to be converted to INT using the operator ABS.
main:(
SHORT SHORT INT ssdec = SHORT SHORT 727,
sshex = ABS SHORT SHORT 16r2d7,
ssoct = ABS SHORT SHORT 8r1327,
ssbin = ABS SHORT SHORT 2r1011010111;
SHORT INT sdec = SHORT 727,
shex = ABS SHORT 16r2d7,
soct = ABS SHORT 8r1327,
sbin = ABS SHORT 2r1011010111;
INT dec = 727,
hex = ABS 16r2d7,
oct = ABS 8r1327,
bin = ABS 2r1011010111;
LONG INT ldec = LONG 727,
lhex = ABS LONG 16r2d7,
loct = ABS LONG 8r1327,
lbin = ABS LONG 2r1011010111;
CO
LONG LONG INT lldec = LONG LONG 727,
llhex = ABS LONG LONG 16r2d7,
lloct = ABS LONG LONG 8r1327,
llbin = ABS LONG LONG 2r1011010111
# etc ... #
END CO
print(("SHORT SHORT INT:", ssdec, sshex, ssoct, ssbin, new line));
print((" SHORT INT:", sdec, shex, soct, sbin, new line));
print((" INT:", dec, hex, oct, bin, new line));
print((" LONG INT:", ldec, lhex, loct, lbin, new line))
CO LONG LONG INT not supported by ELLA ALGOL 68RS
print(("LONG LONG INT:", new line, lldec, new line, llhex, new line, lloct, new line, llbin, new line))
# etc ... #
END CO
)
algol68g output:
SHORT SHORT INT: +727 +727 +727 +727
SHORT INT: +727 +727 +727 +727
INT: +727 +727 +727 +727
LONG INT: +727 +727 +727 +727
algol68toc output:
SHORT SHORT INT: -41 -41 -41 -41
SHORT INT: +727 +727 +727 +727
INT: +727 +727 +727 +727
LONG INT: +727 +727 +727 +727
[edit] AmigaE
PROC main()
IF ($2d7 = 727) AND (%001011010111 = 727) THEN WriteF('true\n')
ENDPROC
[edit] AutoHotkey
If (727 == 0x2d7)
MsgBox true
[edit] AWK
BEGIN {
if ( (0x2d7 == 727) &&
(01327 == 727) ) {
print "true"
}
}
[edit] BASIC
&O = octal; &H = hexadecimal. Some flavors of BASIC also support &B = binary, but they're somewhat rare.
PRINT 17
PRINT &O21
PRINT &H11
Output:
17 17 17
[edit] Befunge
While Befunge doesn't directly support numbers aside from 0-9 (base 10), characters in strings are essentially treated as base-256 numbers.
" ~"..@
Output:
126 32
[edit] C
Leading 0 means octal, 0x or 0X means hexadecimal. Otherwise, it is just decimal.
#include <stdio.h>
int main(void)
{
printf("%s\n",
( (727 == 0x2d7) &&
(727 == 01327) ) ? "true" : "false");
return 0;
}
GCC supports specifying integers in binary using the 0b prefix syntax, but it's not standard. Standard C has no way of specifying integers in binary.
To specify a literal of an unsigned integer, you add the suffix "u" or "U". To specify a literal of a "long" integer, you add the suffix "l" or "L". In C99, to specify a literal of a "long long" integer, you add the suffix "ll" or "LL". (The "l" and "ll" forms are discouraged as "l" looks like the digit "1"). The "u" suffixes can be combined with "l" or "ll" suffixes for unsigned long or unsigned long long integers.
[edit] C#
C# has decimal and hexadecimal integer literals, the latter of which are prefixed with 0x:
int a = 42;
int b = 0x2a;
Literals of either form can be suffixed with U and/or L. U will cause the literal to be interpreted as an unsigned type (necessary for numbers exceeding 231 or hex literals that have a first digit larger than 7) and L signifies the use of a long type – using UL or LU as suffix will then use ulong. C# has no syntactic notion of expressing integer literals of smaller types than Int32; it is a compile-time error to have an assignment such as
byte x = 500;
[edit] C++
The same comments apply as to the C example.
#include <iostream>
int main()
{
std::cout << ( (727 == 0x2d7) &&
(727 == 01327) ? "true" : "false")
<< std::endl;
return 0;
}
[edit] Clojure
Clojure uses the Java octal (0...) and hexadecimal (0x...) notation; for any other base, nR... is used, 2 <= n <= 36.
user=> 2r1001
9
user=> 8r64
52
user=> 064
52
user=> 16r4b
75
user=> 0x4b
75
user=>
[edit] Common Lisp
(This is an interactive common lisp session)
binary: #b, octal: #o, hexadecimal: #x, any base from 2 to 36: #Nr
>(= 727 #b1011010111)
T
>(= 727 #o1327)
T
>(= 727 #x2d7)
T
>(= 727 #20r1g7)
T
[edit] D
D besides hexadecimal, and octal bases has also binary base. Additionaly you can use _ to separate digits in integer literals.
Library: tango
import tango.io.Stdout;
int main(char[][] args)
{
Stdout ("oct: ") (0777).newline;
Stdout ("bin: ") (0b01011010).newline;
Stdout ("hex: ") (0xBADF00D).newline;
Stdout ("dec: ") (1000000000).newline;
Stdout ("dec: ") (1_000_000_000).newline;
Stdout.newline;
Stdout (typeid(typeof(0))).newline;
Stdout (typeid(typeof(0u))).newline;
Stdout (typeid(typeof(0L))).newline;
Stdout (typeid(typeof(0uL))).newline;
Stdout (typeid(typeof(0LU))).newline;
Stdout.newline;
Stdout.formatln ("{:x}", 0xFEE1_BAD_CAFE_BABEuL);
return 0;
}
Output:
oct: 511 bin: 90 hex: 195948557 dec: 1000000000 dec: 1000000000 int uint long ulong ulong fee1badcafebabe
[edit] E
? 256
# value: 256
? 0x100
# value: 256
? 0123
# syntax error: Octal is no longer supported: 0123
[edit] Efene
@public
run = fn () {
io.format("0xff : ~B~n", [0xff])
io.format("0xFF : ~B~n", [0xFF])
io.format("0o777 : ~B~n", [0o777])
io.format("0b1011: ~B~n", [0b1011])
}
[edit] Forth
The standard method for entering numbers of a particular base is to set the user variable BASE to the desired radix from 2 to 36. There are also convenience words for setting the base to DECIMAL and HEX.
HEX
FEEDFACE
2 BASE !
1011001
DECIMAL
1234
: mask var @ [ base @ hex ] 3fff and [ base ! ] var ! ;
The Forth numeric parser will look for symbols embedded within the stream of digits to determine whether to interpret it as a single cell, double cell, or floating point literal ('e').
1234 ( n )
123.4 ( l h )
123e4 ( F: n )
[edit] Base prefixes
Works with: GNU Forth In addition, many Forths have extensions for using a prefix to temporarily override BASE when entering an integer literal. These are the prefixes supported by GNU Forth.
$feedface \ hexadecimal
&1234 \ decimal
%1001101 \ binary
'a \ base 256 (ASCII literal)
Some Forths also support "0xABCD" hex literals for compatibility with C-like languages.
[edit] Fortran
program IntegerLiteral
implicit none
integer, parameter :: dec = 727
integer, parameter :: hex = Z'2d7'
integer, parameter :: oct = O'1327'
integer, parameter :: bin = B'1011010111'
print *, dec, hex, oct, bin
end program IntegerLiteral
Outputs:
727 727 727 727
[edit] Go
Leading 0 means octal, 0x or 0X means hexadecimal. Otherwise, it is just decimal. There is no binary.
package main
import "fmt"
func main() {
if 727 == 0x2d7 && 727 == 01327 {
fmt.Println("true")
} else {
fmt.Println("false")
}
}
[edit] Groovy
Solution:
println 025 // octal
println 25 // decimal
println 0x25 // hexadecimal
Output:
21 25 37
[edit] Haskell
(This is an interactive ghci session)
Oct(leading 0o or 0O), Hex(leading 0x or 0X)
Prelude> 727 == 0o1327
True
Prelude> 727 == 0x2d7
True
[edit] HicEst
HicEst only supports decimal integer literals.
[edit] Icon and Unicon
Icon/Unicon supports digit literals of the form <base>r<value> with base being from 2-36 and the digits being from 0..9 and a..z.
[edit] Icon
procedure main()
L := [1, 2r10, 3r10, 4r10, 5r10, 6r10, 7r10, 8r10, 9r10, 10r10, 11r10, 12r10, 13r10, 14r10,
15r10, 16r10, 17r10, 18r10,19r10, 20r10, 21r10, 22r10, 23r10, 24r10, 25r10, 26r10, 27r10,
28r10, 29r10, 30r10, 31r10, 32r10, 33r10, 34r10, 35r10, 36r10]
every write(!L)
end
[edit] Unicon
This Icon solution works in Unicon.
[edit] J
J's numeric mini-language allows spaces, underlines, dots and lower case alphabetic characters in its numeric literals.
Arbitrary base numbers begin with a base ten literal (which represents the base of this number), and then the letter 'b' and then an arbitrary sequence of digits and letters which represents the number in that base. Letters a..z represent digits in the range 10..35. Each numeric item in a numeric constant must have its base specified independently.
10b123 16b123 8b123 20b123 2b123 1b123 0b123 100b123 99 0
123 291 83 443 11 6 3 10203 99 0
This may be used to enter hexadecimal or octal or binary numbers. However, note also that J's primitives support a variety of binary operations on numbers represented as sequences of 0s and 1s, like this:
0 1 0 0 0 1 0 0 0 1 1 1 1
J also supports extended precision integers, if one member of a list ends with an 'x' when they are parsed. Extended precision literals can not be combined, in the same constant, with arbitrary base literals because of ambiguities regarding the meaning of the letters.
123456789123456789123456789 100000000000x
123456789123456789123456789 100000000000
16b100 10x
|ill-formed number
J also allows integers to be entered using other notations, such as scientific or rational.
1e2 100r5
100 20
Internally, J freely converts fixed precision integers to floating point numbers when they overflow, and numbers (including integers) of any type may be combined using any operation where they would individually be valid arguments.
[edit] Java
Leading 0 means octal, 0x or 0X means hexadecimal. Otherwise, it is just decimal.
public class IntegerLiterals {
public static void main(String[] args) {
System.out.println( 727 == 0x2d7 &&
727 == 01327 );
}
}
Java has no way of specifying integers in binary.
You may also specify a long literal by adding an l or L (the latter form is preferred as the former looks like a "1") to the end (ex: long a = 574298540721727L), and this is required for numbers that are too large to be expressed as an int.
[edit] JavaScript
if ( 727 == 0x2d7 &&
727 == 01327 )
window.alert("true");
[edit] Logo
Logo only supports decimal integer literals.
[edit] Lua
Lua supports either base ten or hex
45, 0x45
[edit] M4
eval(10) # base 10
eval(010) # base 8
eval(0x10) # base 16
eval(0b10) # base 2
eval(`0r2:10') # base 2
...
eval(`0r36:10') # base 36
Output:
10 # base 10 8 # base 8 16 # base 16 2 # base 2 2 # base 2 ... 36 # base 36
[edit] Metafont
num1 := oct"100";
num2 := hex"100";
Metafont numbers can't be greater than 4096, so that the maximum octal and hexadecimal legal values are 7777 and FFF respectively. To be honest, "100" is a string, and oct is an "internal" "macro"; but this is the way Metafont specifies numbers in base 8 and 16.
[edit] Modula-3
All numbers 2 to 16 are allowed to be bases.
MODULE Literals EXPORTS Main;
IMPORT IO;
BEGIN
IO.PutInt(16_2D7);
IO.Put(" ");
IO.PutInt(10_727);
IO.Put(" ");
IO.PutInt(8_1327);
IO.Put(" ");
IO.PutInt(2_1011010111);
IO.Put("\n");
END Literals.
[edit] Objeck
As of v1.1, Objeck only supports hexadecimal and decimal literals.
bundle Default {
class Literal {
function : Main(args : String[]) ~ Nil {
(727 = 0x2d7)->PrintLine();
}
}
}
[edit] OCaml
(This is an interactive ocaml session)
Bin(leading 0b or 0B), Oct(leading 0o or 0O), Hex(leading 0x or 0X)
# 727 = 0b1011010111;;
- : bool = true
# 727 = 0o1327;;
- : bool = true
# 727 = 0x2d7;;
- : bool = true
# 12345 = 12_345 (* underscores are ignored; useful for keeping track of places *);;
- : bool = true
Literals for the other built-in integer types:
- 727l - int32
- 727L - int64
- 727n - nativeint
[edit] Oz
To demonstrate the different numerical bases, we unify the identical values:
try
%% binary octal dec. hexadecimal
0b1011010111 = 01327 = 727 = 0x2d7
{Show success}
catch _ then
{Show unexpectedError}
end
Negative integers start with "~":
X = ~42
[edit] Perl
print "true\n" if ( 727 == 0x2d7 &&
727 == 01327 &&
727 == 0b1011010111 &&
12345 == 12_345 # underscores are ignored; useful for keeping track of places
);
[edit] Perl 6
These all print 255.
say 255;
say 0d255;
say 0xff;
say 0o377;
say 0b1111_1111;
say :10<255>;
say :16<ff>;
say :8<377>;
say :2<1111_1111>;
say :3<100110>;
say :4<3333>;
say :12<193>;
say :36<73>;
There is a specced form for bases above 36, but rakudo does not yet implement it.
[edit] PHP
<?php
if ( 727 == 0x2d7 &&
727 == 01327 )
echo "true\n";
?>
[edit] PicoLisp
In the strict sense of this task, PicoLisp reads only integers at bases which are a power of ten (scaled fixed-point integers). This is controlled via the global variable '*Scl':
: (setq *Scl 4)
-> 4
: 123.456789
-> 1234568
However, the reader is normally augmented by read macros, which can read any base or any desired format. Read macros are not executed at runtime, but intially when the sources are read.
: '(a `(hex "7F") b `(oct "377") c)
-> (a 127 b 255 c)
In addition to standard formats like 'hex' (hexadecimal) and 'oct' (octal), there are also more esoteric formats like 'fmt64' (base 64) and 'hax' (hexadecimal numbers coded with alphabetic characters).
[edit] PL/I
12345
'b4'xn /* a hexadecimal literal integer */
'ffff_ffff'xn /* a longer hexadecimal hexadecimal integer. */
[edit] PowerShell
PowerShell only supports base 10 and 16 directly:
727 # base 10
0x2d7 # base 16
Furthermore there are special suffices which treat the integer as a multiple of a specific power of two, intended to simplify file size operations:
3KB # 3072
3MB # 3145728
3GB # 3221225472
3TB # 3298534883328
A number can be suffixed with d to make it a decimal. This doesn't work in conjunction with above suffixes, though:
PS> 4d.GetType().ToString() System.Decimal
[edit] PureBasic
PureBasic allows integer literals to be specified in base 10, base 2 by using the prefix '%', or base 16 by using the prefix '$'.
x = 15 ;15 in base 10
x = %1111 ;15 in base 2
x = $f ;15 in base 16
An integer literal representing a character code can also be expressed by surrounding the character with single quotes. More than one character can be included in the single quotes (i.e. 'abc'). Depending on whether code is compiled in Ascii or Unicode mode this will result in the integer value being specified in base 256 or base 65536 respectively.
x = 'a' ;129
[edit] Python
Works with: Python version 3.0 Python 3.0 brought in the binary literal and uses 0o or 0O exclusively for octal.
>>> # Bin(leading 0b or 0B), Oct(leading 0o or 0O), Dec, Hex(leading 0x or 0X), in order:
>>> 0b1011010111 == 0o1327 == 727 == 0x2d7
True
>>>
Works with: Python version 2.6 Python 2.6 has the binary and new octal formats of 3.0, as well as keeping the earlier leading 0 octal format of previous 2.X versions for compatability.
>>> # Bin(leading 0b or 0B), Oct(leading 0o or 0O, or just 0), Dec, Hex(leading 0x or 0X), in order:
>>> 0b1011010111 == 0o1327 == 01327 == 727 == 0x2d7
True
>>>
Works with: Python version 2.5
>>> # Oct(leading 0), Dec, Hex(leading 0x or 0X), in order:
>>> 01327 == 727 == 0x2d7
True
>>>
In Python 2.x you may also specify a long literal by adding an l or L (the latter form is preferred as the former looks like a "1") to the end (ex: 574298540721727L), but this is optional, as integer literals that are too large for an int will be interpreted as a long.
[edit] R
0x or 0X followed by digits or the letters a-f denotes a hexadecimal number. The suffix L means that the number should be stored as an integer rather than numeric (floating point).
0x2d7==727 # TRUE
identical(0x2d7, 727) # TRUE
is.numeric(727) # TRUE
is.integer(727) # FALSE
is.integer(727L) # TRUE
is.numeric(0x2d7) # TRUE
is.integer(0x2d7) # FALSE
is.integer(0x2d7L) # TRUE
For more information, see Section 10.3.1 of the R Language definition (PDF).
[edit] Ruby
(This is an interactive irb session)
irb(main):001:0> 727 == 0b1011010111
=> true
irb(main):002:0> 727 == 0x2d7
=> true
irb(main):003:0> 727 == 01327
=> true
irb(main):001:0> 12345 == 12_345 # underscores are ignored; useful for keeping track of places
=> true
[edit] Scala
Scala has signed integers of 8, 16, 32 and 64 bits. They can be represented in decimal, octal by prefixing
0, or hexadecimal by prefixing 0x or 0X. Without any other type hint,
it defaults to 32 bits integers, or an Int. An l or L suffix will
indicate a 64 bits integer, or a Long. The other two types, Byte and Short,
can be represented using type ascription, as shown below.
scala> 16 res10: Int = 16 scala> 020L res11: Long = 16 scala> 0x10 : Byte res12: Byte = 16 scala> 16 : Short res13: Short = 16 scala> 020 : Int res14: Int = 16 scala> 0x10 : Long res15: Long = 16
[edit] Scheme
(This is an interactive scheme session)
binary: #b, octal: #o, decimal: #d (optional obviously), hex: #x
> (= 727 #b1011010111)
#t
> (= 727 #o1327)
#t
> (= 727 #d727)
#t
> (= 727 #x2d7)
#t
[edit] Slate
2r1011010111 + 8r1327 + 10r727 + 16r2d7 / 4
[edit] Standard ML
(This is an interactive SML/NJ session)
Hex(leading 0x), Word (unsigned ints, leading 0w), Word Hex (leading 0wx)
- 727 = 0x2d7;
val it = true : bool
- 727 = Word.toInt 0w727;
val it = true : bool
- 0w727 = 0wx2d7;
val it = true : bool
- ~727; (* negative number; ~ is the unary negation operator for all numbers, including reals and ints; worth mentioning because it's unusual *)
val it = ~727 : int
[edit] Tcl
Works with: Tcl version 8.5 (This is an interactive tclsh session; expr is only called to evaluate the equality test.)
% expr 727 == 0x2d7
1
% expr 727 == 0o1327
1
% expr 727 == 01327
1
% expr 727 == 0b1011010111
1
[edit] TI-89 BASIC
Binary, decimal, and hexadecimal are supported. The system base mode sets the default output base, but does not affect input; unmarked digits are always decimal.
0b10000001 = 129 = 0h81
[edit] UNIX Shell
Works with: bash
As manual states, 0x or 0X is the prefix for hexadecimal numbers, while 0 is the one for octal, and nothing means the number is decimal. But the sintax BASE#NUMBER can be used, with BASE going from 2 to 64, and the symbols used are digits, lowercase letters, uppercase letters, @ and _ in that order; if the BASE is less than or equal to 36, lowercase and uppercase letters can be used interchangeably to represent number from 10 and 35. (From the info manual of the Bash). This syntax works only in some circumstances, i.e. in the shell expansion (e.g. inside $(( ))) or using let.
dec=727
oct=$(( 01327 ))
bin=$(( 2#1011010111 ))
hex=$(( 0x2d7 ))
# or e.g.
let bin=2#1011010111
let "baseXX = 20#1g7"
[edit] Ursala
Natural numbers (i.e., unsigned integers) of any size are supported. Only decimal integer literals are recognized by the compiler, as in a declaration such as the following.
n = 724
Signed integers are also recognized and are considered a separate type from natural numbers, but non-negative integers and natural numbers have compatible binary representations.
z = -35
Signed rational numbers of unlimited precision are yet another primitive type and can be expressed in conventional decimal form.
m = -2/3
The forward slash in a rational literal is part of the syntax and not a division operator. Finally, a signed or unsigned integer with a trailing underscore, like this
t = 4534934521_
is used for numbers stored in binary converted decimal format, also with unlimited precision, which may perform better in applications involving very large decimal numbers.
