Right now it seems the <description> element has no effect on the generated HTML when inside a <typedef> tag nested in a <class>. For instance, I have documented the variant<...>::types typedef, but this is not visible in the generated HTML.
I really don't want to have to use a <purpose> element, since the resultant formatting is amenable only to short blurbs IMO.
Thanks, Eric
P.S. On a related note, it would also be useful to be able to document typedefs that are not nested in a class. I don't know if this is easier or harder to implement than the nested typedef case, but in any case I don't need it now. Just thinking into the future :)
------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! http://www.apachecon.com/ _______________________________________________ Boost-docs mailing list [EMAIL PROTECTED] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
