Hey anons, in C++, I used in some older code an uint (just so to not type unsigned int
everywhere) guard at the very beginning of a header file (actually just a main) that ran fine as then:
#ifndef uint
#define uint unsigned int
#endif // uint
#include <unordered_map>
#include <string>
#include <stdio.h>
...
But that was on a Windows PC. After trying it again, now on a Linux one, that guard conflicts with C++'s own files. If I move the #ifndef
block to after the includes, it compiles without issues.
Would this be compiler related? I don't remember which one I used with Windows back then, however it likely was that one bundled with MinGW.
Any clues as to why that may actualy be happening? Much appreciated at any rate.