There are basically two kinds of numbers in Java and most other programming languages: binary integers (most commonly using the type int) and binary floating-point numbers (most commonly using the type double).

Java Notes

Numbers

Two kinds of numbers. There are basically two kinds of numbers in Java and most other programming languages: binary integers (most commonly using the type int) and binary floating-point numbers (most commonly using the type double). Although these numbers are stored in the computer as binary numbers, you will usually use decimal numbers in your Java source program, and the Java compiler translates them to the equivalent binary form.

Floating-point numbers can have a fractional part and we usually write them with a decimal point, for example, 3.14159265, 0.01, -4.0.

Integers are "whole numbers" and can not have a fractional part. for example, 3, 0, -4.

Typical Issues

• Deciding which to choose: integer or floating-point.
• Be sure the range (minimum to maximum value) is sufficient.
• Be sure the accuracy (number of digits of precision) is sufficient in floating-point.
• Conversions between integer, floating-point, and String.
• Consequences of integer and floating-point arithmetic.

Numbers in Java

• Integers
• Floating-point
• Strings to Numbers

Topics to eventually be added

• BigInteger - Unbounded integer range.
• BigDecimal - Decimal arithmetic.
• IEEE-754 representation of floating-point numbers, including overflow, underflow, infinity, and NaN.
• strictfp

Number FAQ

Q: Isn't it more efficient to use small types (like short) than int?

A: In principle small variables (those using fewer bytes) should be faster than large variables. So on the surface it would seem that you should use, for example, byte for integers that are in the range -128 to +127 because a byte integer requires only 1/4 the memory that an int does.

First, if you have only a small amount of data, as many programs do, the effect would be unmeasurable.

Second, because entire memory blocks are passed between the CPU and RAM there may not actually be any difference for small amounts of data! The exact way that memory is handled in the hardware is complex and often requires benchmarking (actual tests) to determine the speed of various options.

Large amounts of data are another matter, for example, when using arrays. If you're storing millions of numbers, their size has a definite effect on performance.

int and double are the types that the Java compiler likes for integer and floating-point constants and expressions, so you will find it much easier to use them. If you use other sizes of numbers, you will have to write a lot of cast operators, which is annoying and makes your code harder to read. I used to choose the smallest type that would work for my data for efficiency reasons, but have finally given up and just use int and double because of the convenience - except for large amounts of data.

Webliography

• Check out William Kahan's homepage if you want to find out more about the dark corners of floating-point numbers and Java. www.cs.berkeley.edu/~wkahan/

Related Tags for Numbers:
java,  c,  programming,  com,  compiler,  orm,  ui,  form,  binary,  language,  io,  floating-point,  float,  integer,  type,  compile,  double,  numbers,  decimal,  source,  number,  pil,  using,  ole,  int,  action,  write,  languages,  basic,  computer,  for,  poi,  example,  call,  with,  program,  mpi,  to,  point,  ram,  ical,  exam,  store,  ci,  lan,  integers,  bi,  e,  il,  it,  translate,  not,  equivalent,  can,  put,  use,  pe,  im,  art,  ce,  in,  no,  rm,  part,  cal,  as,  m,  nt,  par,  tr,  min,  os,  ca,  min,  os,  j,  es,  em,  compute,  4.0,  common,  all,  alt,  age,  pi,  rc,  pro,  do,  stored,  tor,  bin,  xa,  xamp,  s,  su,  so,  at,  rac,  late,  k,  ha,  ll,  iv,  mpl,  and,  ar,  act,  rt,  va,  tw,  sla,  s,  s,  ri,  th,  sua,  av,  st,  141,  6,  ati,  ica,  ica,  ple,  pl,  pr,  most,  mi,  nd,  only,  on,  om,  ogr,  ol,  o,  nl