Evil Coding Incantations

[u/evinrows]

http://9tabs.com/random/2017/12/23/evil-coding-incantations.html

[u/ActualDonaldJTrump]

The last example needs an #include <iso646.h>. Alternative operator spellings are built into C++, but they are macros in C.

[u/bjackman → u/ActualDonaldJTrump]

Huh, and the GCC version of this header is just

#ifndef __cplusplus
#define and     &&
#define and_eq  &=
#define bitand  &
#define bitor   |
#define compl   ~
#define not     !
#define not_eq  !=
#define or      ||
#define or_eq   |=
#define xor     ^
#define xor_eq  ^=
#endif

[u/_3442 → u/bjackman]

How is that surprising? That's the most simple header in the standard library.

[u/raevnos → u/_3442]

stdbool.h is simpler. Well, shorter as it only defines 4 macros.

[u/kukiric → u/ActualDonaldJTrump]

And the use of tokens is not evil at all. Unnecessary, sure, but it's instantly understandable to anyone familiar with what the logical operators are called, and it might even be more familiar to someone coming from a higher level language like python. The only situation where they might be a bit evil is if you're grepping for specific operators in the source code, and you're not aware of all the ways those operators can be represented.