Why comparing Integer with int can throw NullPointerException in Java?

by

The Short Answer

The key point is this:

  • == between two reference types is always reference comparison
    • More often than not, e.g. with Integer and String, you’d want to use equals instead
  • == between a reference type and a numeric primitive type is always numeric comparison
    • The reference type will be subjected to unboxing conversion
    • Unboxing null always throws NullPointerException
  • While Java has many special treatments for String, it is in fact NOT a primitive type

The above statements hold for any given valid Java code. With this understanding, there is no inconsistency whatsoever in the snippet you presented.

The Long Answer

Here are the relevant JLS sections:

JLS 15.21.3 Reference Equality Operators == and !=

If the operands of an equality operator are both of either reference type or the null type, then the operation is object equality.

This explains the following:

Integer i = null;
String str = null;

if (i == null) {   // Nothing happens
}
if (str == null) { // Nothing happens
}
if (str == "0") {  // Nothing happens
}

Both operands are reference types, and that’s why the == is reference equality comparison.

This also explains the following:

System.out.println(new Integer(0) == new Integer(0)); // "false"
System.out.println("X" == "x".toUpperCase()); // "false"

For == to be numerical equality, at least one of the operand must be a numeric type:

JLS 15.21.1 Numerical Equality Operators == and !=

If the operands of an equality operator are both of numeric type, or one is of numeric type and the other is convertible to numeric type, binary numeric promotion is performed on the operands. If the promoted type of the operands is int or long, then an integer equality test is performed; if the promoted type is float or double`, then a floating-point equality test is performed.

Note that binary numeric promotion performs value set conversion and unboxing conversion.

This explains:

Integer i = null;

if (i == 0) {  //NullPointerException
}

Here’s an excerpt from Effective Java 2nd Edition, Item 49: Prefer primitives to boxed primitives:

In summary, use primitives in preference to boxed primitive whenever you have the choice. Primitive types are simpler and faster. If you must use boxed primitives, be careful! Autoboxing reduces the verbosity, but not the danger, of using boxed primitives. When your program compares two boxed primitives with the == operator, it does an identity comparison, which is almost certainly not what you want. When your program does mixed-type computations involving boxed and unboxed primitives, it does unboxing, and when your program does unboxing, it can throw NullPointerException. Finally, when your program boxes primitive values, it can result in costly and unnecessary object creations.

There are places where you have no choice but to use boxed primitives, e.g. generics, but otherwise you should seriously consider if a decision to use boxed primitives is justified.

References

Related questions

Related questions

More Related Contents:

  1. Android, NullPointerException
  2. What is a NullPointerException, and how do I fix it?
  3. NullPointerException accessing views in onCreate()
  4. Which @NotNull Java annotation should I use?
  5. How to convert int[] into List in Java?
  6. Convert an array of primitive longs into a List of Longs
  7. NullPointerException in Java with no StackTrace
  8. Error invoke virtual method ‘double android.location.Location.getLatitude()’ on a null object reference
  9. Filter values only if not null using lambda in Java8
  10. Why does int num = Integer.getInteger(“123”) throw NullPointerException?
  11. In Java 8, is there a ByteStream class?
  12. How large is the Integer cache?
  13. Why static fields are not initialized in time?
  14. Java conditional operator ?: result type
  15. JPA/Hibernate Static Metamodel Attributes not Populated — NullPointerException
  16. Apache POI – FileInputStream works, File object fails (NullPointerException)
  17. Spring Boot – Environment @Autowired throws NullPointerException
  18. Compiler error : reference to call ambiguous
  19. Why can I throw null in Java? [duplicate]
  20. java.lang.NullPointerException: Attempt to invoke virtual method on a null object reference [duplicate]
  21. Is Catching a Null Pointer Exception a Code Smell?
  22. NullPointerException stack trace not available without debug agent
  23. Gracefully avoiding NullPointerException in Java
  24. Attempt to invoke virtual method ‘void android.widget.Button.setOnClickListener(android.view.View$OnClickListener)’ on a null object reference
  25. How to convert byte[] to Byte[] and the other way around?
  26. Which @NonNull Java annotation to use [duplicate]
  27. How to trace a NullPointerException in a chain of getters
  28. Why ternary operation gives nullpointer while its ifelse counterpart doesn’t? [duplicate]
  29. Android: java.lang.NullPointerException: Attempt to invoke virtual method ‘java.lang.String java.lang.Object.toString()’ on a null object reference
  30. How do I avoid checking for nulls in Java?

Leave a Comment