Re: [Doxygen-develop] Bug in 1.4.0?

[Dan G. <dan...@gm...>]

On Mon, 3 Jan 2005 14:19:25 -0800, Cadle, Brad <bc...@ar...> wrote:
> I noticed that in moving from version 1.3.9.1 to 1.4.0 the behavior of the \todo command seems have been broken:
> 
> in 1.3.9.1 all the /todo commands for a single C function are grouped under a single heading in the file reference.
> 
> In 1.4.0 Each /todo command in the file reference for a single function results in a separate heading in the file reference.
> 
> Example:
> 
>    /** \todo Fill out function. */
> 
>    /** \req Complies with requirement squiggy */
> 
>    /** \ps Test Psuedo Code line 1 \endps */
> 
>    /** \todo Remove ret = 1. *
> 
> (NOTE: /ps is an alias I defined)
> 
> 1.3.9.1, I get for the file reference
> 
> Todo:
>     Fill out function.
> 
>     Remove ret = 1.
> 
> Requirements:
>     Complies with requirement squiggy
> 
> Pseudo Code:
>     Test Psuedo Code line 1
> 
> 1.4.0, I get for the file reference
> 
> Todo:
>     Fill out function.
> 
> Requirements:
>     Complies with requirement squiggy
> 
> Pseudo Code:
>     Test Psuedo Code line 1
> 
> Todo:
>     Remove ret = 1.
> 
> Clearly, 1.3.9.1 is desirable.
> 

This may be a result of a bug fix (id 157485) I'll let Dimitri comment
further.

I've also noticed peculiar behavior with alias/xrefitem entries in
function bodies (I don't believe it is new though).  For example in my
Doxygen configuration file I define an alias "future" to be a
xrefitem.  I use @future inside of function bodies following a ///
comment delimiter.  Sometimes Doxygen will complain about an unknown
\future command (with a slightly inaccurate source line number) and
the text following the @future gets merged with the previous
paragraph.  I can work around the problem by putting a blank /// ahead
of it.  I will eventually characterize this better and submit a bug
but I thought I would mention it if you were in the area :-).

Kudos (and many thanks) Dimitri for your quality software.  I have
been active in some Python related open source activities and am
getting an appreciation for how much work and dedication goes into
projects like this.

Best Regards,
Dan Gass