boost-preprocessor

Not sure what to make of this error. Added -D_WIN32_WINNT=0x0501 to Visual Studio's "Command Line" options under Project Properties but it says it doesn't recognize it and the warning still appears. I am also not sure how to add the Preprocessor Definition. 1>Please define _WIN32_WINNT or _WIN32_WINDOWS appropriately. For example: 1>- add -D_WIN32_WINNT=0x0501 to the compiler command line; or 1>- add _WIN32_WINNT=0x0501 to your project's Preprocessor Definitions. I think you're really close to getting this to work. John Dibling gave three ways you could do this and it looks like you tried the

I am trying to figure out what version of Boost my code thinks it's using. I want to do something like this: #error BOOST_VERSION but the preprocessor does not expand BOOST_VERSION. I know I could print it out at run-time from the program, and I know I could look at the output of the preprocessor to find the answer. I feel like having a way of doing this during compilation could be useful. If you are using Visual C++, you can use #pragma message : #include <boost/preprocessor/stringize.hpp> #pragma message("BOOST_VERSION=" BOOST_PP_STRINGIZE(BOOST_VERSION)) Edit: Thanks to LB for link

I'm trying to do some kind of Macro "Overloading", so that MACRO(something), gets expanded differently than MACRO(something, else). Using a snippet I got from here (I'm not sure if it's 100% portable) and some functions from the Boost PP Library, I was able to make it work :D //THESE TWO COUNT THE NUMBER OF ARGUMENTS #define VA_NARGS_IMPL(_1, _2, _3, _4, _5, N, ...) N #define VA_NARGS(...) VA_NARGS_IMPL(__VA_ARGS__, 5, 4, 3, 2, 1) //THIS ONE RETURNS THE PARAMETER AT POSITION _i FROM A LIST OF __VA_ARGS__ #define VA_ARG(_i, ...) BOOST_PP_ARRAY_ELEM(_i, (VA_NARGS(__VA_ARGS__), (__VA_ARGS__))) /

For example class A { int m_x; float m_y; double m_z; int x() const {return m_x;} float y() const {return m_y;} double z() const {return m_z;} }; becomes like class A { MY_MACRO((int)(float)(double), (x)(y)(z)); }; Please use boost prerocessor sequence to do it because this macro will combine with other existing macros which already use boost preprocesor sequence. cv_and_he Disclaimer:You should probably wait in case a better answer appears even if you are satisfied with this answer, because I'm far from an expert and these may not be the best approaches. 1st approach: //two different

I would like to have include file paths dynamically created by a macro for a target-configuration-dependent part of my program. for example, I would like to construct a macro that would be invoked like this: #include TARGET_PATH_OF(header.h) Which will expand to a something like this: #include "corefoundation/header.h" when the source is configured (in this case) for OSX So far all attempts have failed. I'm hoping someone out there has done this before? example of what does not work: #include <iostream> #include <boost/preprocessor.hpp> #define Dir directory/ #define File filename.h #define

After discovering the Boost preprocessor's capabilities I found myself wondering: Is the C99 preprocessor Turing complete? If not, what does it lack to not qualify? Here is an example of abusing the preprocessor to implement a Turing machine. Note that an external build script is needed to feed the preprocessor's output back into its input, so the preprocessor in and of itself isn't Turing complete. Still, it's an interesting project. From the description of the afore-linked project: the preprocessor is not Turing complete, at least not if the program is preprocessed only once. This is true