On May 8, 2013, at 21:01 , damon_car...@ltxc.com wrote: > > Hi > > I have noticed in version 1.8.3.1.-20130402 that the @copydoc has a > different behavior. If I use @copydoc to document a member function from > the contents of another member function, for example, > > /** @par Description > Here is some stuff about this function */ > void func2() > > /** @copydoc func2() */ > void func3() > > the one that used @copydoc (func3 in this example) has an unexpected > "More..." link in the page function list. The original that was copied > (func2) does not. I find the problem goes away if I use @copydetails rather > than @copydoc. > > I don't know if this is correct behavior that I don't understand or if it > is a bug. Version 1.8.3 and 1.7.5 do not show this behavior. Can someone > enlighten me?
The "More..." links were recently added (for consistency), but should only appear if there is a brief and a detailed description. @copydoc is internally replaced by a pair of @copybrief and @copydetails commands. The check to see if a brief description is present is done on the input text (i.e. the text including the @copybrief command), not on the result after parsing (which would be an empty string in your particular case). I'll based the check on the result after parsing, which will fix the problem you see. Regards, Dimitri ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may _______________________________________________ Doxygen-users mailing list Doxygen-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/doxygen-users
