Re: FW: [Doxygen-develop] Extracting more source struture in XML output

[Chris C. <do...@ke...>]

(Emailed to OP as well as to the list, the sourceforge list server was
bouncing my mails, I don't know if it still is doing so...)

On Tue, Oct 05, 2004 at 01:42:07PM -0700, Pau...@no... wrote:

> Doxygen's XML schema is a good starting point to add to if I want a
> complete XML representation of the code, so I would like to add to it
> rather than invent another schema. Also can anyone give me some
> pointers where I would change the Doxygen code to output more source
> code structure? Doxygen must know much of this information anyway, as
> it has some more detailed information in the highlight elements of the
> source file XML files.

I would very much like a C/C++ to XML translator, which seems to be what
you are suggesting as a possibility (or an extreme version of what you
are suggesting).  As you say it opens up a lot of possibilities for
extra tools, as well as for having doxygen produce internal
documentation (like local variables, tables of which functions use which
global variables (set and read), etc.  It needs to be switchable,
though.

While I'm thinking about switches, it would be very useful to have
options settable from the command line, not just in the configuration
file.  For some purposes I have to maintain three or more versions of
the config file (implementer detail, user detail, overview, sometimes
with or without relationship charts as well), a switch to set options
would be a lot easier to put in a makefile with a common config file for
all the messy stuff (include/exclude lists, etc.).  Oh, and the version
number.  Or have I missed something which already allows this?

Chris C