On Sat, Oct 20, 2012 at 11:05 AM, Earnie Boyd
<[email protected]>wrote:
> 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.
>
Yes it is definitely following a different path. It just seems odd to me
that...it would pull in entire include files in one path but not another
(intrin.h *only* on win64).
-r
------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
