Hi, > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Doug > Gregor > > On Aug 13, 2004, at 8:07 PM, Eric Niebler wrote: > > I'm still interested in turning on > > preprocessing, but the above isn't doing it. I have added > > <doxygen:param>PREDEFINED=BOOST_DEDUCED_TYPENAME=typename, in the > > hopes that it would replace all occurances of > "BOOST_DEDUCED_TYPENAME" > > with "typename" in the code, but it didn't work. Why?>> > > Possibly nothing. This is likely a Doxygen bug, where it doesn't > follow its own parameters sometimes in the XML it outputs. To > double-check this, see if BOOST_DEDUCED_TYPENAME shows up in the > generated ".doxygen" XML output anywhere.
XML output is "raw", some configuration settings, which apply to HTML output do not apply to XML output, although they seem global from their name. Unfortunately, it is not documented. I do not know exactly, if this is the case here. Are you sure that you have set: ENABLE_PREPROCESSING = YES MACRO_EXPANSION = YES EXPAND_ONLY_PREDEF = YES (only if you want the macros in sources untouched, see EXPAND_AS_DEFINED) > > For each entity, I have a brief description and a detailed > > description. The brief description ends up at the top of > the generated > > HTML file (good), but the detailed description ends up > orphaned at the > > bottom (bad). There is a "Description" section in the HTML > following > > the "Synopsis" section, but it is always empty. Bug? As I said above; e.g. settings automatic brief description and duplicated brief description are processed for the final documentation targets like HTML, not XML. You have separated <briefdescription /> and <detaileddescription /> just like they were provided in sources. It is not even consistent between /// and /** */, from historical reasons. I did a patch for doxygen for comment consolidation and I'm going to offer it in its mailing list (always brief in <brief... /> and only detailed without brief in <detailed... />). You can also sort it out in XSL, with some effort (e.g. take detailed if there is no brief, and join brief with detailed for the complete documentation). > > And if I want to change the filename that a class appears in, the > > Doxygen guide says I can do it with the /class directive, but it > > doesn't seem to have any effect. I do not understand it. Do you want to document a class in a separate file and not above its declaration? Then you are right about \class Xxx::Yyy. Ferda ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 _______________________________________________ Boost-docs mailing list [EMAIL PROTECTED] Unsubscribe and other administrative requests: https://lists.sourceforge.net/lists/listinfo/boost-docs
