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 739209 - Invalid warning about undocumented C++ function imported from tagfile [with test case]
Invalid warning about undocumented C++ function imported from tagfile [with t...
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.8-GIT
Other All
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2014-10-26 14:55 UTC by Vladimír Vondruš
Modified: 2014-12-25 16:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Repro/test case (739 bytes, application/zip)
2014-10-26 14:55 UTC, Vladimír Vondruš
Details

Description Vladimír Vondruš 2014-10-26 14:55:42 UTC
Created attachment 289350 [details]
Repro/test case

See attached ZIP file for minimal repro case. I disabled all output, as it is not needed to reproduce this. Generate the tagfile and process it using the following commands:

    doxygen Doxyfile.original
    doxygen Doxyfile.current

The first command generates `original.tag` file, the second parses it and outputs the following warning:

    <unknown>:1: warning: Member member() (function) of class Foo< int > is not documented.

Other than that the generated documentation (if enabled) would be generated okay, with all crosslinks. See `current.h` file -- the issue appears only when subclassing from template, when changing the line to `struct Bar: Foo {};`, the warning disappears (and the generated documentation would still be okay).

Tested with current Git (a31c9ff), this issue appeared "since forever" (I don't know when I first came around this warning, but I think it was present in 1.7 already). I'm currently working around this by running `doxygen | grep -v "<unknown>"`, but it's annoying :)
Comment 1 Dimitri van Heesch 2014-12-23 11:10:33 UTC
Confirmed. Should be fixed in the next GIT update.
Comment 2 Dimitri van Heesch 2014-12-25 16:02:34 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.9. 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 (preferrably in the form of a self-contained example).