I agree, it would be much better if this was picked up at compile time - took a while searching and head scratching before I figured out what the problem was.
>> You can get around this by increasing the maximum size a variant can handle,And one more question: if I define these macros in some TU of my
>> define the following symbols (or higher if you need):
>>
>> #define BOOST_MPL_LIMIT_LIST_SIZE 30
>> #define BOOST_MPL_LIMIT_VECTOR_SIZE 30
>> #define BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS
project, in the way that affects some other boost headers I include --
should I define them when building boost as well?
_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users