Originally Posted By: Riamus2

But, this starts to become too much, imo:
if ((this == that) || (this == that)) { }


Actually thats the only right way to avoid ambiguity and the way alot of languages will FORCE you to do it. I actually prefer this style since it's easer to understand how the if is evaluated just as ((2 - 4) * 2) is easier to understand than 2 - 4 * 2 both are valid but yet yield different values because of the ambiguity in the latter.

The test posted above is wrong on many levels i.e "If 1 <= 2 noop | noop" .... i'll let you figure out why thats wrong yourself.

Then theres the issue you only test 1 condition if statements when comparisons get complex, i have a good hunch using all the proper ()'s will speed it up. I tested this some versions back but i'm unable to find my post on here. but as starbucks_mafia put it very well here
Quote:

Whether that's still true, whether that's always true, and whether the speed benefits actually matter or not, I don't know.