19 Feb
2006
19 Feb
'06
6:07 p.m.
David Abrahams wrote:
This one is easy. Just run the tool twice, once with the macro defined and once without.
Not if there's more than one of them: it becomes a 2^N problem.
Oh far, more than that. Consider something like:
-DBOOST_MPL_MAX_SEQUENCE_LENGTH=40
The value of this macro affects which headers get included.
But this particular macro is application specific, ergo should be constant for all different compiler configurations. The problematic part are the compiler dependent config macros, IMHO. Regards Hartmut