Comments on: Brain hurting mistakes of our time http://www.magpiebrain.com/blog/2004/01/13/brain-hurting-mistakes-of-our-time/ Sam Newman's blog Sat, 05 Jul 2008 00:41:57 +0000 http://wordpress.org/?v=2.5.1 By: migs http://www.magpiebrain.com/blog/2004/01/13/brain-hurting-mistakes-of-our-time/#comment-150 migs Wed, 28 Jan 2004 04:33:38 +0000 http://www.magpiebrain.com/2004/01/13/brain-hurting-mistakes-of-our-time/#comment-150 Making ActionErrors final (which I do by habit) would've spotted the first case. Making ActionErrors final (which I do by habit) would’ve spotted the first case.

]]> By: jef http://www.magpiebrain.com/blog/2004/01/13/brain-hurting-mistakes-of-our-time/#comment-149 jef Mon, 19 Jan 2004 20:28:32 +0000 http://www.magpiebrain.com/2004/01/13/brain-hurting-mistakes-of-our-time/#comment-149 wheee! For that matter, you'll also get the behavior that boolean c = true; boolean b = false; if(b=c) { System.out.println("text"); } will always print, but if (c=b) { System.out.println("text"); } will never print. Probably caused more than one VB developer to give up... Once I spent an hour trying to figure out why if (somemethodcall(c)); { System.out.println("text"); } would always print even as I stepped again and again through the method observing that I hadn't botched the logic and that it really should be returning false... wheee!
For that matter, you’ll also get the behavior that

boolean c = true;
boolean b = false;

if(b=c) {
System.out.println(“text”);
}

will always print, but

if (c=b) {
System.out.println(“text”);
}

will never print. Probably caused more than one VB developer to give up… Once I spent an hour trying to figure out why

if (somemethodcall©);
{
System.out.println(“text”);
}

would always print even as I stepped again and again through the method observing that I hadn’t botched the logic and that it really should be returning false…

]]> By: R.J. http://www.magpiebrain.com/blog/2004/01/13/brain-hurting-mistakes-of-our-time/#comment-148 R.J. Tue, 13 Jan 2004 18:28:49 +0000 http://www.magpiebrain.com/2004/01/13/brain-hurting-mistakes-of-our-time/#comment-148 Yeah, it's an interesting little known feature of Java assignment operators. In terms of 'operator overloading', it is essentially 'returning' the value of the assignment after performing the assignment on the variable. That's why: boolean c = true; boolean b = false; if(b=c) { System.out.println("text"); } compiles and prints out text; unlike: if(b==c) { ... } which doesn't. Yeah, it’s an interesting little known feature of Java assignment operators. In terms of ‘operator overloading’, it is essentially ‘returning’ the value of the assignment after performing the assignment on the variable.
That’s why:
boolean c = true;
boolean b = false;
if(b=c) {

System.out.println(“text”);
}
compiles and prints out text; unlike:
if(b==c) {
...
}
which doesn’t.

]]>