Hartmut Kaiser wrote
Hartmut Kaiser wrote Well, if there was an error that states that there are too few or too many macro arguments, that means somewhere during scanning/rescanning there was a macro invoked with too many/few arguments. So, the lowest macro replacement which caused this error and what the parameter set that was passed would be AWESOME!
Isn't that what you see in the trace you sent in the very end? There you see
BOOST_PP_SEQ_ELEM_III(BOOST_PP_SEQ_ELEM_0)
right before the output stops. Further up you can see, that this particular problem occurs while trying to expand
BOOST_PP_SEQ_ELEM_II(BOOST_PP_SEQ_ELEM_2 (volatile)(const))
Ahhh, yes, that's it. Couldn't see the tree for the forest. :/ Thanks, fixed now. Adrian -- View this message in context: http://boost.2283326.n4.nabble.com/boost-wave-trace-doesn-t-output-errors-tp... Sent from the Boost - Dev mailing list archive at Nabble.com.