Op 12 okt. 2017 11:15 a.m. schreef "Frédéric" <[email protected]>:
> If you look at MSDN, it's actually _WIN32 is the only macro really > mentioned anywhere. WIN32 is defined by most Visual studio projects at that > level, not the compiler. So in my eyes, changing code to check for _WIN32 > is the only right thing to do. Yes and on our suggestion, the library has just done that (changing WIN32 to _WIN32). However, why does w64 treat differently -std=gnu++XX than -std=c++XX? This does not look consistent to me as WIN32 is not concerned by the standard. That is a good question. I would say it is something decided long ago and now either still there due to no one working on changing that, or there is a valid reason this is required. If no one here answers your question, you might try the GCC mailing list, although not a lot of Windows developers lurk there.. Ruben F ------------------------------------------------------------ ------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
