3 ms·
The last one is terrible ... I have seen #define TRUE 0 #define FALSE 1 back in the day. Too bad there was no source control in the company then, so I could
by venomsnake 14y ago
The last one is terrible ... I have seen
#define TRUE 0
#define FALSE 1
back in the day.
Too bad there was no source control in the company then, so I could not find out who was responsible for that travesty and "talk calmly" some sense into them.
- mappu 14y agoProcesses (and a common design for c functions) return zero on success and an error code otherwise. Although it might be unexpected (and certainly breaks flow constructs), it's probably not so bad with some context. Worse, though, Windows defines TRUE and FALSE for you somewhere in windef.h - so you would have to be careful about where your code was included..
- deleted 14y ago[deleted]
- deleted 14y ago[deleted]