On Fri, Oct 19, 2012 at 3:19 PM, Roger Pack wrote: >>> Who is defining const as an empty macro? That doesn't seem right. >> >> >> C++ only makes it undefined behavior, and the rules are fuzzy at best (seems >> that it's only undefined behavior when the translation unit includes a >> standard header): >> http://stackoverflow.com/questions/2726204/c-preprocessor-define-ing-a-keyword-is-it-standards-conforming >> >> In C, it seems that it is allowed. >> >> All this doesn't change the fact that #define const is incredibly stupid and >> should be removed from user code. > > Agree. > My confusion though is still why, with the same include (windows.h) in > 64 bit it also loads intrin.h, but not in 32 bit. odd...
It is most likely because _WIN64 takes on different characteristics. I.E. The same path isn't followed in the header code when _WIN64 is defined. -- Earnie -- https://sites.google.com/site/earnieboyd ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
