From: Hartmut Kaiser (hartmutkaiser_at_[hidden])
Date: 2003-04-07 09:24:58
Hi all,
If you ever had the need to debug a macro expansion you had to discover,
that your tools provide only little or no support for this task. For
this reason the Wave library got a unique tracing facility, which allows
to get selectively some information from the expansion of a certain
macro or several macros.
The tracing facility is plugged into the library through a policy, which
allows for its easy customization. The Wave command line driver utilizes
this new feature to generate a complete log containing information about
every stage of the expansion of a macro under inspection, which allows
to easily analyze foreign code or to debug your own problematic macros.
A complete description of the new tracing feature you may find in Wave
the documentation
(http://spirit.sourceforge.net/index.php?doc=docs/wave_v0_9/index.html)
or inside the downloadable files).
As always, you can download the Wave library
http://spirit.sourceforge.net/index.php?doc=download/Wave_0_9.html.
Regards Hartmut
BTW: If you ever wanted to know, how the Boost.Preprocessor library
works behind the scenes, now you are able to inspect, how it works. The
Boost.Preprocessor library contained as a part of the V1.30.0 release
already is aware of the Wave preprocessor, so you may use it together.