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 761007 - Spaces between the closing bracket of the typename and the opening bracket of the parameter list cause detection issues.
Spaces between the closing bracket of the typename and the opening bracket of...
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: build
unspecified
Other All
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2016-01-22 22:10 UTC by download-fritz
Modified: 2016-09-05 13:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Four images showing the used code and its generated documentation. (68.34 KB, application/x-zip-compressed)
2016-01-22 22:10 UTC, download-fritz
Details

Description download-fritz 2016-01-22 22:10:24 UTC
Created attachment 319576 [details]
Four images showing the used code and its generated documentation.

When typedefs involving a parameter list (function typedefs) are formated with a space between the closing bracket of the typename and the opening bracket of the parameter list, the Doxygen parser does not document it correctly, understanding the last string of the parameter list to be the typename rather than the desired typename within the first set of brackets.

Four images have been attached to illustrate the issue, as I believe they show the issue better than I am capable of explaining it. The two with the prefix 'Space' are those taken from the original source, the space included, and the two with the 'NoSpace' prefix show the modified source and its correctly(!) generated documentation.
Comment 1 albert 2016-01-24 10:34:37 UTC
Images are nice and say indeed often more than a description but to reproduce the problem a small example with the output (and the above given description) is better.

I've just pushed a proposed solution to github (pull request 447)
Comment 2 albert 2016-01-24 12:16:22 UTC
Patch has been included in github version
Comment 3 Dimitri van Heesch 2016-09-05 13:45:39 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.12. 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).