My boss said I should use null == obj
, because it's better than obj == null
, but he didn't remember why to do this. Is there any reason for using null == obj
?
I feel it somehow... opposite!
After some search on Google, the only thing I found is:
in C, it prevents you accidentally from typing (obj = null) in a conditional structure.
There is absolutely no difference in either semantics or performance. The == in this case is a reference inequality operation; it can never throw NullPointerException .
A null object refers to an object without any reference or an object defined with neutral/null functionality/behavior. These null objects need to be checked to ensure that they are not null while accessing any member or invoking any methods.
out. println("(Object)string == number: " + ((Object)string == number)); To conclude this post and answer the titular question Does null equal null in Java? the answer is a simple yes.
7. == and != The comparison and not equal to operators are allowed with null in Java.
You can't accidently assign null
to obj
by typing obj = null
instead. However, that's a reminiscence from C times, in java, it is not possible, as the =
expression returns the right hand side of the assignment. As null
is not a boolean
, the compiler will complain.
I would try to explain it to my boss once, demonstrate it. If he still doesn't agree with you, just do it. It's a petty thing to fight about with your boss.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With