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
Found ';' while parsing initializer list! for member function pointer #10369
Comments
Note: current doxygen version is 1.9.8
|
@albert-github I added an example that shows the problem. Unfortunately, I can only use 1.9.5 at the moment. |
I see the warning with the versions 1.9.5, 1.9.8 and the current master (1.10.0 (81b6518)) also these versions have no relevant differences regarding this problem (as far as I can see quickly) |
So there is no solution for this problem at the moment? Interestingly, maybe this helps, if the return type of the function is changed to |
Interesting observation, might have to do with the handling of the |
I do not know. Do you have a clue for a solution? |
It is a difficult problem especially due to all the new "improvements" in the different standards that complicate things here (and also for compiler builders etc.) . |
The easiest workaround (that also helps to make the code more readable) is to define a type, e.g. /** Name for this type */
using ThisType = Foo<dim,NumberType>;
/** 3D Type */
using Type3D = Foo<3,NumberType>;
/**
* Pointer to member func 1
*/
Type3D(ThisType::*funcPtr)(const Type3D &arg1) const; |
@swiesheier Please verify if the referenced commit fixes the problem for you. Do not close the issue, this will be done automatically when the next official version is released. |
This issue was previously marked 'fixed but not released', |
I use doxygen 1.9.5 and get
warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)
for the docu of a member function pointer in c++
If I remove the template brackets for the return type,
doxygen treats it as a function and reports
Is there a preprocessor trick to work around this issue?
UPDATE:
I attached a minimal example demonstrating the problem!
mwe.cc.tar.gz
The text was updated successfully, but these errors were encountered: