Comments on: Java: String Equality (Common Mistake) http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/ A passionate programmer's findings in the world of internet. Tue, 27 Jul 2010 15:27:18 -0400 hourly 1 http://wordpress.org/?v=3.0 By: Rick O'Shay http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/comment-page-1/#comment-90047 Rick O'Shay Tue, 03 Nov 2009 22:50:44 +0000 http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/#comment-90047 The == operator generally works because the strings are pooled. String variables with the same contents usually end up "pointing" to the same object. If you rely on this optimization, sooner or later you will get burned. Consider a servlet where the incoming strings from a request are not defined as string constants but rather dynamically allocated. You should compare strings using the "equals" method, not the == operator. The == operator generally works because the strings are pooled. String variables with the same contents usually end up “pointing” to the same object.

If you rely on this optimization, sooner or later you will get burned. Consider a servlet where the incoming strings from a request are not defined as string constants but rather dynamically allocated. You should compare strings using the “equals” method, not the == operator.

]]> By: Thank you http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/comment-page-1/#comment-86625 Thank you Thu, 20 Aug 2009 07:06:59 +0000 http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/#comment-86625 Thank you, good post! Thank you, good post!

]]> By: Seyfi http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/comment-page-1/#comment-85915 Seyfi Mon, 03 Aug 2009 10:08:26 +0000 http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/#comment-85915 thanks a lot ;) thanks a lot ;)

]]> By: Umakant http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/comment-page-1/#comment-84789 Umakant Wed, 17 Jun 2009 22:47:38 +0000 http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/#comment-84789 hey dude thank you very much............. i have just wasted my 4 hours to do this......... thanx hey dude thank you very much………….

i have just wasted my 4 hours to do this………

thanx

]]> By: Bobby LeMain http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/comment-page-1/#comment-84590 Bobby LeMain Thu, 11 Jun 2009 17:25:47 +0000 http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/#comment-84590 I was messing around with this the other day. Apparently there was an update, because String b = "b"; if(b == "b") //returns true as a .NET programmer would expect I was messing around with this the other day. Apparently there was an update, because

String b = “b”;
if(b == “b”)
//returns true as a .NET programmer would expect

]]> By: PROG [JAVA] - 9lives http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/comment-page-1/#comment-80804 PROG [JAVA] - 9lives Sat, 28 Feb 2009 13:42:44 +0000 http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/#comment-80804 [...] Gurdt das nie echt waar wa gij zegt he == vergelijk heel basisch de linker met de rechterkant Java: String Equality (Common Mistake) - enrii.blog dat dus. misschien gewoon slecht verwoord. __________________ Gamertag: [...] [...] Gurdt das nie echt waar wa gij zegt he == vergelijk heel basisch de linker met de rechterkant Java: String Equality (Common Mistake) – enrii.blog dat dus. misschien gewoon slecht verwoord. __________________ Gamertag: [...]

]]> By: destrukthorts http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/comment-page-1/#comment-76138 destrukthorts Fri, 31 Oct 2008 21:31:02 +0000 http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/#comment-76138 Thanks!, im doing a java version of a simple, solid, python process, thx a lot :-b Thanks!, im doing a java version of a simple, solid, python process, thx a lot :-b

]]> By: JavaLearner http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/comment-page-1/#comment-76087 JavaLearner Thu, 30 Oct 2008 00:35:09 +0000 http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/#comment-76087 Thank you ! I can now explain this to my daughter who is doing Java in high school. Thank you ! I can now explain this to my daughter who is doing Java in high school.

]]> By: Static on WAQ177 » Java: String Equality (Common Mistake) - enrii.blog http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/comment-page-1/#comment-73308 Static on WAQ177 » Java: String Equality (Common Mistake) - enrii.blog Fri, 25 Jul 2008 03:45:19 +0000 http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/#comment-73308 [...] [From Java: String Equality (Common Mistake) - enrii.blog] [...] [...] [From Java: String Equality (Common Mistake) - enrii.blog] [...]

]]> By: EngLee http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/comment-page-1/#comment-51467 EngLee Thu, 03 Jan 2008 01:53:09 +0000 http://blog.enrii.com/2006/03/15/java-string-equality-common-mistake/#comment-51467 Feel free to correct me. I'm no expert in Java string handling, I'm just writing based on my experience. When I encounter problem, I find solution and I blog about it. The example given is simply to show how two strings that look the same would go wrong when comparing with "==". Most of the time, a programmer would have done some string manipulations before they compare the strings. After some manipulations, whether you declare with new or not, you will go wrong with "==". Anyway, why do you need to declare 2 strings with the same value? Feel free to correct me. I’m no expert in Java string handling, I’m just writing based on my experience. When I encounter problem, I find solution and I blog about it.

The example given is simply to show how two strings that look the same would go wrong when comparing with “==”. Most of the time, a programmer would have done some string manipulations before they compare the strings. After some manipulations, whether you declare with new or not, you will go wrong with “==”.

Anyway, why do you need to declare 2 strings with the same value?

]]>