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 refers to incorrect line for undocumented member function (C++) (Origin: bugzilla #755939) #5879

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

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status VERIFIED severity normal in component general for ---
Reported in version 1.8.11-GIT on platform Other
Assigned to: Dimitri van Heesch

On 2015-10-01 13:28:56 +0000, csaba_22@yahoo.co.uk wrote:

When warning about undocumented member functions, the reported line number is that of the class, not the undocumented member function.

For example, when generating docs for the following class:
/** A small man
*/
struct miniman { // <--------- line 3
/// Here's some documentation
void doc();

    void undoc(); // <--------- line 7

};

I get the following warning:

/tmp/miniman.h:3: warning: Member undoc() (function) of class miniman is not documented.

The line number should be that of the undocumented member, i.e. line 7

$ doxygen --version
1.8.11

On 2015-10-02 09:15:54 +0000, csaba_22@yahoo.co.uk wrote:

Note: works correctly with 1.8.9.1

On 2015-12-28 18:56:00 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2015-12-30 10:20:24 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.11. 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 (preferably in the form of a self-contained example).

On 2016-01-12 11:47:06 +0000, csaba_22@yahoo.co.uk wrote:

Verified with 1.8.11 release.

@doxygen doxygen closed this Jul 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment