Edward Diener-3 wrote
You should be able to look at wave's output and see exactly the sequence of macro expansions which cause the error you are seeing.
One would think that. Unfortunately, this is not the case. I don't quite understand it. The output is good, but there are errors in expansion. I've attached the trace here http://boost.2283326.n4.nabble.com/file/n4646830/trace.7z . Maybe you can see where the problem is? It's only 16 thousand plus lines. If wave's trace could state "hey, this is where the expansion failed!", that would be a great time saver. 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.