> I used to look for programmers who wrote "if(3 = = foo)" rather than
> "if(foo = = 3)" 

Despite the hows and whys, this is still a cute trick, rather than a good 
proccess. 

The statement "if(3==foo)" is written in the opposite way to how you 
would describe what the statement is doing, so the statement isn't 
immediately and inherently self documenting.

More importantly, the method only works for one instance in a collection 
of related mistakes. ie. mistyped operators.
You are just as likely to type "if(foo=3)" when you meant to type  
"if(foo==3)" as you are to type "if(foo & 3)" when you meant to type  
"if(foo && 3)".  

If you had intended to use ==, &&, ||, >> or << and only used a single 
character, transposed operands would only be an error in 1 of the 5 
cases. A procedure that only works 20% of the time, isn't that good a 
procedure.

Steve.



_______________________________________________
http://www.piclist.com
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist