= Should only test for equality, this was a bug in the design of C, which got FIXED in Pascal<br>:= Is assignment<br>The other weakness C was that == (a test for equality) was just too easy to get confused with =<br>So in Pascal, this was fixed, and = tests for equality ONLY<br><br>This is a huge step backwards, and breaks two fixes... and does it backwards<br><br>This is more programmer hostile that the stupid decision to make C and Python case sensitive.<br><br>Signed - Grump old pascal programmer,(reply>), @Mike Warot It's not a bug.  With Python at least, there are string methods that can be used relatively easily to determine that you are talking about the same person.  Just cast everything to lowercase or uppercase, and this isn't a problem.  By being able to compare cases, now you can check for proper grammar, as "Mike" would need to be capitalized in English, being a proper noun.,(reply>), @Science Compliance We already have the convention that Mike, MIKE, mike, are all the same person.... just because someone was too lazy to write a better string comparison routine in a compiler in the 1960s is no reason to stick us all with that bug today, especially in a newer language.,(reply>), Why is case sensitivity a bad thing?  Not only are upper and lowercase different characters, but allowing sensitivity to these different characters expands the palette of characters that can be used in a program.  What I mean by that is that a single character / byte can be used to represent more information with a larger set of distinct characters available.