lol, those were pretty good

... What are they talking about? I see nothing wrong with that program snippet syntactically, why do they say it won't compile?



This post was edited by Minkomonster on Nov 4 2014 07:11am

Strange, does your compiler have the womyn extension to compensate for poor syntax?

Since assignment doesn't exist within an if, maybe it just assumes you're retarded and meant something else.

Not even Python does that.



At least it produces warnings.

Warning != syntax error

And assignment does exist within an if which is why it is perfectly valid c code. The warning came after. The reason being back in the day before coding standards were more established, c was focused purely on performance. And there are cases where doing assignments inside the if condition resulted in code that was more performant.

The warning came later to let newbie c++ programmers know that they might have botched their comparison because they don't understand the difference between assignment and comparison and also don't understand that c syntax allows for both in an if.

Anything else?

This post was edited by Minkomonster on Nov 4 2014 09:50am

Don't hate on the coding illiterate.

This, we're people too.



This post was edited by killg0re on Nov 4 2014 10:18am

I am not hating on anyone. I was explaining how the assumption that there was a syntax error was wrong. And further explaining that your attempt to troll me by calling my compiler a woman and compensating for my mental capacity was also wrong. And further explaining that your defense of those who called that person out for her tweet for her compliation errors was dead wrong in every way possible. Sure, the code does not follow standard practices and there definitely are some logic errors.but there are NOT syntax errors.

I don't have much experience in C/C++ didn't realize it was so forgiving for minor syntax errors. The syntax is incorrect though, the compiler recognizes this and warns you, so it is still an error even if it doesn't crash.

Python cuts dead if you mix up == and = operators in the syntax, many other languages do too.

Since operators are part of the code arrangement, they are still technically part of the syntax, though the compiler seems to not care if about this error and only passes warnings.

Your real mistake was taking their comment literally, it visually had syntax mistakes and was called out immediately, it is not like anyone actually tried to run her garbage twitter troll bait. Finally, the comment "0/0 WOULD NOT COMPILE" is a play on the popular internet-idiom would not fuck, which has nothing to do with actually compiling the code but with the posters disgust at the terrible syntax.

Why do I have to explain this?

You keep saying syntax errors. There are NO syntax errors. Warnings are there to catch potential logical errors. The syntax is 100% valid. 0 errors. Logically there may be discrepancies. Hence the Warning. Are you getting it now?

If the syntax is incorrect, even if it compiles, it is still an error or else the compiler wouldn't have to warn you of the syntax being incorrect.