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

Template static member functions duplicated as non-static public (Origin: bugzilla #700696) #5186

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

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component documentation for ---
Reported in version 1.8.4 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2013-05-20 08:44:14 +0000, geoff@telesiscomputing.com.au wrote:

Created attachment 244759
Example header and settings file.

A template static member function, whether public or protected, will duplicate in the documentation as non-static public. You get a warning about the member not being documented even though it is. Documentation attaches to the invalid non-static public rather than the correct static method. Example that generates the problem:

/! \brief This class is documented./
class AClass {
public:
template static char* astaticfunc(C ainput);
};

/*! \brief This function is documented /
template
char
AClass::astaticfunc(C achar)
{ return nullptr; }

This above included in attachment with relevant settings file.

On 2013-05-20 08:45:32 +0000, geoff@telesiscomputing.com.au wrote:

It may be worth cross-referencing with my previous report: https://bugzilla.gnome.org/show_bug.cgi?id=700693 because that is also a duplicate documentation issue related to templates, so it seems possible the problems may be related.

On 2013-05-20 10:50:03 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2013-05-20 18:03:13 +0000, Dimitri van Heesch wrote:

*** Bug 700202 has been marked as a duplicate of this bug. ***

On 2013-08-23 15:04:52 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.5. 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