Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

In Java:

int count = (Integer) null;

throws a java.lang.NullPointerException.

Why doesn't this throw a Class Cast Exception for ease in programmer understanding?

Why was this exception chosen over any other exception?

share|improve this question
add comment

2 Answers

up vote 30 down vote accepted

When executing your code, the Java runtime does the following:

  1. Cast null to an object of class Integer.
  2. Try to unbox the Integer object to an int by calling the method intValue()
  3. Calling a method on a null object throws a NullPointerException.

In other words, null can be cast to Integer without a problem, but a null integer object cannot be converted to a value of type int.

EDIT

I had a related question a while ago at Stack Overflow, see here.

share|improve this answer
add comment

Java successfully casts null to an Integer reference that references no object.

That's OK because being unistantiated is a valid state for a reference.

It's the calling of a method of a non existing object that can't be performed.

Performing the cast (Integer)null is the same as declaring an Integer variable and then failing to assign it an new (or already existing) Integer object instance.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.