typedef warning when "using" some operator functions (Origin: bugzilla #700709)

[doxygen]

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

Original attachment names and IDs:

• demodox.zip (ID 244768)

On 2013-05-20 12:41:34 +0000, geoff@telesiscomputing.com.au wrote:

Created attachment 244768
Example header and settings.

I have something like the following (slightly odd, but legitimate C++11 (according to gcc at least) and the reason for it is more apparent in the full code):

/! \brief This class is documented./
class ABaseClass {
public:
bool operator==(const ABaseClass& arhs) const noexcept;
bool operator!=(const ABaseClass& arhs) const noexcept;
bool operator<(const ABaseClass& arhs) const noexcept;
bool operator<=(const ABaseClass& arhs) const noexcept;
bool operator>(const ABaseClass& arhs) const noexcept;
bool operator>=(const ABaseClass& arhs) const noexcept;
};

/! \brief This class is documented./
class ADerivedClass : public ABaseClass {
public:
using ABaseClass::operator==;
using ABaseClass::operator!=;
using ABaseClass::operator<;
using ABaseClass::operator<=;
using ABaseClass::operator>;
using ABaseClass::operator>=;
};

Doygen gives the following warnings:

demodox.hpp:21: Warning: documented symbol typedef ADerivedClass::ABaseClass::operator' was not declared or defined. demodox.hpp:22: Warning: documented symbol typedef ADerivedClass::ABaseClass::operator' was not declared or defined.
demodox.hpp:24: Warning: documented symbol typedef ADerivedClass::ABaseClass::operator' was not declared or defined. demodox.hpp:26: Warning: documented symbol typedef ADerivedClass::ABaseClass::operator' was not declared or defined.

Notice that it complains about only four of the six using statements (==, !=, <=, >=). It causes no actual problems that I can see, just the unwanted warnings.

Example header and settings file in attachment. Settings use EXTRACT_ALL=YES to avoid having to add unnecessary documentation to the example).

On 2013-05-20 17:54:33 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2013-08-23 15:04:42 +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.