You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On 2012-02-17 14:59:34 +0000, Martin Sauerhoff wrote:
Created attachment 207856
Files for reproducing the bug
In the example below, doxygen omits the documentation of
all class members of class B. It correctly includes the documentation, if
either a space is inserted between the two right double brackets
of type definition StrangeType; or
the (single) member of class A is commented out.
Thus, the parser somehow get's confused by multiple angle brackets.
Note that the two consecutive right angle brackets here are allowed
according to C++11. The dependence on the unrelated definition
of class A is strange, anyway.
//! \file myclass.h
#pragma once
// -----------------------------------------------------------------------------
// Class A
//
//! \brief First class.
// -----------------------------------------------------------------------------
class A
{
static const size_t LargeValue = ~static_cast<size_t>(0);
};
// -----------------------------------------------------------------------------
// Class B
//
//! \brief Second class.
// -----------------------------------------------------------------------------
class B
{
public:
//! Template type with double right angle brackets.
typedef TemplateType1<TemplateType2<T, U>> StrangeType;
//! Member that doxygen refuses to document.
B();
//! Member that doxygen refuses to document.
void undocumentedMemberFunctioncompare();
};
On 2012-02-18 13:19:34 +0000, Dimitri van Heesch wrote:
Confirmed. Should be fixed in the next subversion update.
On 2012-02-25 15:37:20 +0000, Dimitri van Heesch wrote:
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.0. 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.
The text was updated successfully, but these errors were encountered:
status RESOLVED severity normal in component general for ---
Reported in version 1.7.6.1 on platform Other
Assigned to: Dimitri van Heesch
Original attachment names and IDs:
On 2012-02-17 14:59:34 +0000, Martin Sauerhoff wrote:
On 2012-02-18 13:19:34 +0000, Dimitri van Heesch wrote:
On 2012-02-25 15:37:20 +0000, Dimitri van Heesch wrote:
The text was updated successfully, but these errors were encountered: