>> But I never thought of using the MS SDK with MinGW. I guess I could try that.
It won't work with MinGW. Having the MS SDK on hand is good for extracting any definitions that aren't in the MinGW Win32API headers.
Originally Posted by laserlight
Interesting observation. According to the C++ Standard, those keywords should be available and thus not defined as macro names in <ciso646>, but a little experimentation with VS 2005 shows that if you #include <ciso646>, those keywords will work.
Yeah but that is wrong. Like you said in C++ they aren't macros, they are keywords.