re: Why using Yoda conditions you should probably not be VIEW POST

TOP OF THREAD FULL DISCUSSION
re: In some languages (like java) yoda-conditions also give you null handling: if (variable.equals("value")) ... throws an exception if variable is n...
 

Can you really call it a "Yoda condition"?

Yoda conditions have been born to avoid hard-to-catch mistakes, like an assignment in a condition statement. If variable is null in your first example you catch it immediately, because it throws a NullPointerException as you mentioned.

So it doesn't save you from a mistake; it saves you from checking if the value is null or not. And honestly I'm not sure it's what I'd want: if I expect a string there, why am I dealing with null?

code of conduct - report abuse