Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

warning for "lonely <li> tag" does not tell file name nor line number (Origin: bugzilla #633891) #4002

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity minor in component general for ---
Reported in version 1.7.2 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2010-11-03 10:01:35 +0000, Clemens wrote:

Created attachment 173758
minimal example, config file and warning output

If a "lonely"

  • list item statement is used in the comments while but someone forgot to put the
      ,
    statements then doxygen outputs a warning:

    👎 warning: lonely

  • 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

  • ".
    Doxygen should be able to tell the filename and the line number of the problematic "lonely
  • ".

    Maybe this is related to bug 632217 (https://bugzilla.gnome.org/show_bug.cgi?id=632217)

  • On 2010-11-03 10:20:15 +0000, Clemens wrote:

    I found out that the problem seems to be related to "in-body-docs" as in the following example.

    /**
    Test function.

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

    }

    U:/doxygen/li.c:4: warning: lonely

  • tag found
    👎 warning: lonely
  • tag found

  • On 2010-11-07 12:47:59 +0000, Dimitri van Heesch wrote:

    Confirmed. Should be fixed in the next subversion update.

    On 2011-01-03 19:01:28 +0000, Dimitri van Heesch wrote:

    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.

    @doxygen doxygen closed this Jul 2, 2018

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    You can’t perform that action at this time.