Skip to content
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

C++11 "using" type alias for function pointer with no arguments is formatted incorrectly (Origin: bugzilla #759402) #5917

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant
Copy link

doxygen commented Jul 2, 2018

status RESOLVED severity minor in component general for ---
Reported in version 1.8.10 on platform Other
Assigned to: Dimitri van Heesch

On 2015-12-13 12:07:05 +0000, Freddie Chopin wrote:

The following code produces documentation where the type alias is formatted incorrectly.

-- >8 -- >8 -- >8 -- >8 -- >8 -- >8 --

/// \file

/// function pointer
using FunctionPointer = void(*)();

-- >8 -- >8 -- >8 -- >8 -- >8 -- >8 --

This produces a documentation that looks like this:

using FunctionPointer) = void(*)(

While it should look like this:

using FunctionPointer = void(*)()

The same is true for type alias for function reference.

This happens only when the function takes no arguments and if there is no space between parentheses. Following two type aliases produce correct documentation:

using FunctionPointer = void()( ); // space between parentheses
using FunctionPointer = void(
)(char); // function takes arguments

On 2016-10-18 19:34:36 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed by this GIT commit:
SHA: d4c24c2

On 2016-12-29 18:45:45 +0000, Dimitri van Heesch wrote:

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

@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
You can’t perform that action at this time.