Reversing the order of a condition to avoid hard-to-find assignment problems

conditions.php

<?php

//This is what I normally do:
if($something == "string") { ... }

//The problem is, if I accidentally miss an = then it would be an assignment!
if($something = "string") { /* uh oh! */ }

//To prevent this, get in the habit of reversing the order:
if("string" == $something) { ... }

//That way, if you miss an = and it becomes an assignment, it will throw an error!
if ("string" = $something) { /* you can't assign a value to a constant! */ }

LOL just learned that these are called "Yoda Conditions".

More info about Yoda Conditions: http://wiert.wordpress.com/2010/05/25/yoda-conditions-from-stackoverflow-new-programming-jargon-you-coined/ (via @mikealmond)

Yes they are yoda conditions, they are also an archaism from the times of C.

A reason to avoid this archaism:

http://stackoverflow.com/questions/2955304/why-many-programmers-use-integer-literal-on-left-handside-of-equality-operator/2955522#2955522

ok, if (18 <= age) return true; is a little crazy. Definitely wouldn't do that!

But then you end up with inconsistant code :P

I would probably only use the Yoda condition in scary situations, like sending an important email. Situations where not making a mistake is worth the inconsistent condition.
if ("fire" == $command) {
$DeathStar->lasers->fire("Alderaan");
}

Clearly you mean:

if 'fire' == command then lasers.fire

or you can do it this way if you are really paranoid

if command.==('fire') then lasers.fire

fixed :)

But mine was real code too :P

$DeathStar2 = new DeathStar(); //The Empire Strikes Back!

your code doesn't look like PHP - is it Ruby?

yes it is ruby... I likes me some ruby every once in a while

Uncle Bob doesn't like it when people code that way:

http://thecleancoder.blogspot.com/2010/09/john-macintyres-clean-code-experience-1.html