If it was incorrect syntax it wouldn't compile. Warnings don't warn for bad syntax. Warnings warn for possible logic errors. They are two separate things.

The syntax was incorrect, but it didn't break, it only warned that it was incorrect.

There was definitely a logical error, for one she tried to use assignment where it doesn't belong, but that is also a problem of syntax.

You're taking things too literally here, the syntax is incorrect, or there wouldn't be a warning to use the correct operator.

Your arguing Apple's and oranges. You just don't understand what a compiler warning is. You don't understand how a compiler operates and you don't understand the difference between syntax errors and logic errors.

Should just give up here.

Its syntactically correct, you can make assignments inside if statements all you want. The logic however is incorrect. Thus why it would throw a warning. Syntax != warnings.

Example:



Another example:



I use assignments in if statements all the time if I know I need to use it in the logic inside the if statement.

A more practical example:




This post was edited by AbDuCt on Nov 4 2014 02:51pm

Pwned, okay you win