Closed reister-kenneth closed 1 year ago
AIX! Very interesting; we'd love to know what WJE has found its way into there. :^)
As for the conflict itself, I suppose we could surround with an #ifndef or something. I don't foresee any problem with allowing and using an external definition, unless the distinction between signed long and signed int is meaningful to your data.
Two updates.
<string>
still chains to stdint.h causing the same issue
typedef signed long int32;
typedef signed int int32;
typedef signed short int32;
Our code
On AIX
Compile output
<iterator>
had a whole chain that leads to inttypes.h. inttypes.h does #include<stdint.h>
which defines this:I will note that I've solved this one already for us as we were not using
<iterator>, <list>, or <vector>
in that file, so I just removed them.