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

Spaces between the closing bracket of the typename and the opening bracket of the parameter list cause detection issues. (Origin: bugzilla #761007) #5938

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component build for ---
Reported in version unspecified on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2016-01-22 22:10:24 +0000, download-fritz@outlook.com wrote:

Created attachment 319576
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.

On 2016-01-24 10:34:37 +0000, albert wrote:

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)

On 2016-01-24 12:16:22 +0000, albert wrote:

Patch has been included in github version

On 2016-09-05 13:45:39 +0000, Dimitri van Heesch wrote:

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).

@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