After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 759402 - C++11 "using" type alias for function pointer with no arguments is formatted incorrectly
C++11 "using" type alias for function pointer with no arguments is formatted ...
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.10
Other All
: Normal minor
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2015-12-13 12:07 UTC by Freddie Chopin
Modified: 2016-12-29 18:45 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Freddie Chopin 2015-12-13 12:07:05 UTC
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
Comment 1 Dimitri van Heesch 2016-10-18 19:34:36 UTC
Confirmed. Should be fixed by this GIT commit:
https://github.com/doxygen/doxygen/commit/d4c24c28ffcf7143bcdfecee1c8b55f704274d37
Comment 2 Dimitri van Heesch 2016-12-29 18:45:45 UTC
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).