"Jeff Garland" <[EMAIL PROTECTED]> writes:
Doug wrote:
>> (Interestingly, this was one of the complains about Doxygen's output: that it
>> puts nested classes at the same level as their logical enclosing classes)
>
> That's ugly...
>
>> The situation is worse for files: they only tell you what namespaces are used
>> in the file, not what other entities are in the file. For classes, structs,
>> and unions, we have a way out with the <includes> element, which tells us
>> what header file to include to get that entity (we can compare the header
>> name against the header file for which we're generating BoostBook).
>> Unfortunately, namespace-level typedefs, functions, and enumerations don't
>> have the <includes> element, so I'll need to find a better way.
>
> Hmm, that's not good. And yes, the <includes> gives you the data you want
> for classes.
>
>> I'd rather not post the resulting HTML until I get a little further. If you'd
>> like to try it out, you'll want Doxygen 1.2.18: 1.2.17 generates bad XML as
>> does 1.3-rc2 and the current CVS.
>
> At some point we really should feed back our results to the Doxygen development
> group. Maybe we can get them to fix the XML output and make it a bit more
> friendly for boost-book conversion. Of course I'll help when we get a bit
> further...
FWIW, there's some indication that it may be really easy to get
exactly what we want out of Synopsis. I'll let you all know as we
learn more...
--
David Abrahams
[EMAIL PROTECTED] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Boost-docs mailing list
[EMAIL PROTECTED]
Unsubscribe and other administrative requests:
https://lists.sourceforge.net/lists/listinfo/boost-docs
