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 633891 - warning for "lonely <li> tag" does not tell file name nor line number
warning for "lonely <li> tag" does not tell file name nor line number
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.2
Other Windows
: Normal minor
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2010-11-03 10:01 UTC by Clemens
Modified: 2011-01-03 19:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
minimal example, config file and warning output (2.87 KB, application/zip)
2010-11-03 10:01 UTC, Clemens
Details

Description Clemens 2010-11-03 10:01:35 UTC
Created attachment 173758 [details]
minimal example, config file and warning output

If a "lonely" <li> list item statement is used in the comments while but someone forgot to put the <ol>, </ol> statements then doxygen outputs a warning:

<unknown>:-1: warning: lonely <li> tag found

Doxygen has a good reason to output this warning, but note that the warning does neither tell the file name nor the line number. 

It is difficult to identify where the problem is and to fix the "lonely <li>".
Doxygen should be able to tell the filename and the line number of the problematic "lonely <li>".

Maybe this is related to bug 632217 (https://bugzilla.gnome.org/show_bug.cgi?id=632217)
Comment 1 Clemens 2010-11-03 10:20:15 UTC
I found out that the problem seems to be related to "in-body-docs" as in the following example.

/**
Test function.
<li> warning format is OK
*/
void main(void)
{
    int a;
    
    /// <li>  warning format is BAD.
    a++;
} 

U:/doxygen/li.c:4: warning: lonely <li> tag found
<unknown>:-1: warning: lonely <li> tag found
Comment 2 Dimitri van Heesch 2010-11-07 12:47:59 UTC
Confirmed. Should be fixed in the next subversion update.
Comment 3 Dimitri van Heesch 2011-01-03 19:01:28 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.3. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant.