Weird Integer boxing in Java

by

The true line is actually guaranteed by the language specification. From section 5.1.7:

If the value p being boxed is true,
false, a byte, a char in the range
\u0000 to \u007f, or an int or short
number between -128 and 127, then let
r1 and r2 be the results of any two
boxing conversions of p. It is always
the case that r1 == r2.

The discussion goes on, suggesting that although your second line of output is guaranteed, the first isn’t (see the last paragraph quoted below):

Ideally, boxing a given primitive
value p, would always yield an
identical reference. In practice, this
may not be feasible using existing
implementation techniques. The rules
above are a pragmatic compromise. The
final clause above requires that
certain common values always be boxed
into indistinguishable objects. The
implementation may cache these, lazily
or eagerly.

For other values, this formulation
disallows any assumptions about the
identity of the boxed values on the
programmer’s part. This would allow
(but not require) sharing of some or
all of these references.

This ensures that in most common
cases, the behavior will be the
desired one, without imposing an undue
performance penalty, especially on
small devices. Less memory-limited
implementations might, for example,
cache all characters and shorts, as
well as integers and longs in the
range of -32K – +32K.

More Related Contents:

  1. How can I properly compare two Integers in Java?
  2. How to convert int[] into List in Java?
  3. Why do people still use primitive types in Java?
  4. Why do we use autoboxing and unboxing in Java?
  5. Returning null as an int permitted with ternary operator but not if statement
  6. How does auto boxing/unboxing work in Java?
  7. Booleans, conditional operators and autoboxing
  8. Java: Array of primitive data types does not autobox
  9. Why does int num = Integer.getInteger(“123”) throw NullPointerException?
  10. NullPointerException through auto-boxing-behavior of Java ternary operator
  11. Is autoboxing possible for the classes I create?
  12. Why does autoboxing make some calls ambiguous in Java?
  13. Why aren’t Integers cached in Java?
  14. What code does the compiler generate for autoboxing?
  15. Comparing boxed Long values 127 and 128
  16. Is it guaranteed that new Integer(i) == i in Java?
  17. Java Arrays.asList on primitive array type produces unexpected List type [duplicate]
  18. Java autoboxing and ternary operator madness
  19. When using == for a primitive and a boxed value, is autoboxing done, or is unboxing done
  20. How do I convert Double[] to double[]?
  21. Java: What’s the difference between autoboxing and casting?
  22. Does autoboxing call valueOf()?
  23. NullPointerException with autoboxing in ternary expression
  24. Why doesn’t autoboxing overrule varargs when using method overloading in Java 7?
  25. Java Modifying Elements in a foreach
  26. java : Understanding Arrays.asList(T…array) method for primitive types
  27. Does Java autobox when assigning an int to an Object?
  28. Java Date month difference
  29. java how expensive is a method call
  30. Simplest way to iterate through a Multiset in the order of element frequency?

Leave a Comment