This week's giveaway is in the EJB and other Java EE Technologies forum.
We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line!
See this thread for details.
The moose likes Programmer Certification (SCJP/OCPJP) and the fly likes Wrapper-Method-Q Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Certification » Programmer Certification (SCJP/OCPJP)
Bookmark "Wrapper-Method-Q" Watch "Wrapper-Method-Q" New topic
Author

Wrapper-Method-Q

Vishnu Prakash
Ranch Hand

Joined: Nov 15, 2004
Posts: 1026


why b1.toString() == b2.toString() is evaluating to false.


Servlet Spec 2.4/ Jsp Spec 2.0/ JSTL Spec 1.1 - JSTL Tag Documentation
Mike Gershman
Ranch Hand

Joined: Mar 13, 2004
Posts: 1272
why b1.toString() == b2.toString() is evaluating to false.


When a Java expression creates a new String at run time, a new object is created. The = operator checks whether these are the same object. The equals() method would compare the characters in these objects and yield true.

"127" == "127" would be true because the String object "127" is created once at compile time in the String Literal Pool, so you are comparing an object to itself. When you use toString() to create a String, you get a unique object every time.


Mike Gershman
SCJP 1.4, SCWCD in process
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Wrapper-Method-Q
 
Similar Threads
Please explain this output
Doubt on "=="
Understanding Byte and == Op
* Byte == comparision
toString( ) method