| Author |
wrapper and == question
|
Mark Uppeteer
Ranch Hand
Joined: Mar 02, 2004
Posts: 159
|
|
Hi, I don't understand why prints true. and doesn't. I thought when 'new' is involved you are actually bypassing the cache of the classes. Which seems to be so in the second example, but this doesn't seem to be the case in the first example (where there is a new involved)) Could someone explain this ? thanks!
|
I know where my towel is. (SCJP 5, OCPJWCD)
[Free Quiz Tips for a fun night with friends or family] Flash games
|
 |
Keith Lynn
Ranch Hand
Joined: Feb 07, 2005
Posts: 2341
|
|
The reason is that the return type of Boolean.parseBoolean is a primitive boolean. When == is applied to a boolean and a Boolean, then the Boolean is unboxed and == is boolean equality.
|
 |
Mark Uppeteer
Ranch Hand
Joined: Mar 02, 2004
Posts: 159
|
|
oops,that was actually something I should have been able to see myself.. I guess I was blinded by the 'new' and got confused. Thanks a lot! regards, Mark
|
 |
 |
|
|
subject: wrapper and == question
|
|
|