Name: Anonymous 2014-06-24 16:40
I have read once about the dilemma that some C programmers face: that of writing == for equality comparison and = for assignment.
Specifically when using ==, one might mistakenly write = instead. In some cases, the compiler will catch one red-handed, and in the other cases, it will not, potentially causing bugs.
The solution I have used, even before having read about this problem, is a simple
The question is, am I a nigger?
Specifically when using ==, one might mistakenly write = instead. In some cases, the compiler will catch one red-handed, and in the other cases, it will not, potentially causing bugs.
The solution I have used, even before having read about this problem, is a simple
#define EQU ==
, followed by using only EQU for equality comparisons. For personal reasons, this seemed preferrable to using ==.The question is, am I a nigger?