That's why I write comparisons like

if (CONSTANT == variable)

"yoda conditions":

http://stackoverflow.com/questions/2349378/new-programming-j...

I know it's safer, but personally I find it harder to read. Especially if the constant is a #define or enum and is similar in format to the variable in question.

I personally like Yoda Conditions, but a few coworkers have pointed out that any linter worth its salt will catch an = inside a conditional, so this doesn't actually gain much in safety. I've stopped using them because there a large number of coworkers find them confusing.

Yoda conditions, those are called.

http://united-coders.com/christian-harms/what-are-yoda-condi...

Maybe I am feeling dense, but I do not understand what you are trying to point out. None except one are errors as they relate to embedded sql statements (where Equal To is the comparison operator).

maybe we re seeing different results. mine have 8 incorrect assignments in the first page

The code is generating code for a different language -- the = is always in a string.