RE: [Doxygen-users] Doxygen testing (was: hide undocumented enums )

[Trevor R. <Tre...@pe...>]

I agree.  The key to testability is componentization, and separate C++->XML,
XML->HTML, XML->RTF, XML->tex, and XML->man components are much easier to
test than a single C++->HTML/etc component.  They are even easier to test
than C++->"internal data structures" and "internal data
structures"->HTML/etc components.

Of course this really makes one wish that GCC-XML had a stable release.
However, I imagine that Doxygen could easily have full intermediate XML long
before that.  (Especially since GCC-XML is based on GCC 3.0, which is an
elusive release as well.)

-Trevor


-----Original Message-----
From: Jens-A. Reinhardt [mailto:fl...@un...]
Sent: Monday, June 11, 2001 3:04 PM
To: dox...@li...
Subject: Re: [Doxygen-users] Doxygen testing (was: hide undocumented
enums)



> Maybe verification on the XML output level would be more robost, but
> with the current XML output a lot of information would be missed.
>
> So, any ideas are welcome!

...and what about expanding the XML output?

It would help realizing the needs of a lot of of doxygen users.

Let it be the ones looking for more .css options or fancy design stuff,
the ones that need to add other (non doxygen) content, those who want to
add, drop, rearrange the output, or it would even help testing as you
suggested yourself. Everything could be done without touching the core
code and without the chance of messing up your code.

But I saw that letting XML become an intermediate format is on your todo
list with a rather high difficulty number. However, I guess it would
simplify a lot of things once established and the new modularity will
enable others to contribute more easily and help further development.

Jens





_______________________________________________
Doxygen-users mailing list
Dox...@li...
http://lists.sourceforge.net/lists/listinfo/doxygen-users