After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 157485 - @todo link missing on todo page
@todo link missing on todo page
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: build
1.3.x
Other All
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2004-11-05 22:25 UTC by Dan Gass
Modified: 2009-08-20 10:12 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dan Gass 2004-11-05 22:25:03 UTC 
1) create files:

<file name="aa.h">
#ifndef FNC
#define FNC
void f(void);
#endif
</file>

<file name="zz.c">
#include "aa.h"
/// @todo header
void f(void)
{
    /// @todo function
}
</file>

2) Run doxygen, processing aa.h then zz.c (order is important))

3) Observe a link for the @todo in the function never shows up on the todo page
Comment 1 Dimitri van Heesch 2005-01-01 12:07:30 UTC 
Please verify that this is fixed in release 1.4.0 and if so please close this bug.
Comment 2 Dan Gass 2005-03-23 15:21:14 UTC 
I took the sample code and tried it with 1.4.1 and the problem still exists
Comment 3 Ben Fischer 2009-07-31 15:12:55 UTC 
This problem still persists with version 1.5.9 but I found a simple solution for this:

Edit file commentscan.l, line 519. Change "if (lii & append)" to "if (lii)". Don't understand what "append" is used for anyway, it's set in setOutput() but always to "false"! Checking "lii" is enough and produces correct TODO (and BUG etc.) lists and no items are missing anymore.
Comment 4 Dimitri van Heesch 2009-08-14 14:58:16 UTC 
Should be fixed in the next subversion update.
Comment 5 Dimitri van Heesch 2009-08-20 10:12:46 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.0. Please verify if this is indeed the case and reopen the
bug if you think it is not fixed (include any additional information that you
think can be relevant).