[Doxygen-develop] wish: in-source macro expansion control

[Simon A W. <sim...@ph...>]

I have been using Doxygen on a diverse project, and incorporated it into
our build process.  Once limitation I have encountered is in the control
of which pre-processor macros should be expanded.

Currently we have to specify in the Doxygen configuration file which
macros should be expanded when generating the docs, unless an
all-or-nothing approach is used.

But, we have a general config file for a series of sub-projects.

What would be nice is if there could be a command, associated with the
documentation for a macro, to say whether that macro should be expanded
or not.  Something like:
	
	/// @expand
	#define MYMACRO(ARG1,ARG2) ...

	/// @noexpand
	#define KEY_SIZE 123


If this was the case, I'd probably set Doxygen not to expand anything by
default, and just expand what I've requested (which would mostly be
code-generating macros in my case).

Of course, I could instigate this now by using using "grep" on the
source files (since make already explicitly accumulates a list of the
source files), and append to the EXPAND_AS_DEFINED config option. 
Though for that I'd have to use "/// @expand MYMACRO(ARG1,ARG2)" type
syntax instead. 



Si.


-- 
Simon A Watts
Software Engineer
Philips Medical Systems
mailto:sim...@cl...
tel: +44(0) 1252 747 311