Hartmut Kaiser wrote
If wave's trace could state "hey, this is where the expansion failed!", that would be a great time saver.
What do you mean by that? Where should it point to? The uppermost invocation site? The lowermost macro replacement which failed, somewhere in between?
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! Cheers! 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.