AMDG Dave Jenkins wrote:
This flag sounds the same as the BOOST_COMPILE_TIME_DEBUG flag proposed by Eric Niebler here: http://lists.boost.org/boost-users/2009/01/44451.php. Joel de Guzman suggested making it an integer (0 == no CT debug, 1..3 CT debug levels) here: http://lists.boost.org/boostusers/2009/01/44452.php.
My thought is to have one of the integer debug levels enable compile-time tracing of "interesting" template instantiations using Steven Watanabe's template_profiler. For this to work, the library author would have to mark the "interesting" template classes and functions with "PROFILE_TRACER()" and bypass Steven's preprocessing stage. Is this workable and/or a good idea?
I've been slowly working on getting the call graph info working. In order to do this correctly I have to parse the warning backtrace. This mechanism I am using will break if not every template instantiation is traced. In Christ, Steven Watanabe