-
-
Notifications
You must be signed in to change notification settings - Fork 201
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
Fix crash when visiting typedef #547
Conversation
I know this has issues with |
I did mess around a bit with something similar a few weeks ago doing some testing, based upon #534 (comment) and of course other comments on the issue, but somehow I forgot to finalise things and turn it into a PR. Thanks for creating one. Edit:
I suspect very old code / legacy stuff, I have been maintaining since 2018 but there is still a lot of voodoo going on that I can't wrap my head around (yet). |
I was expecting someone to send it, but got tired of waiting! :-)
Well, we have |
Yeah that's definitely fine, if I |
@jakobandersen Could you also take a look just in case? |
When using the @typedef <name> doxygen command, the generated XML does not have a proper definition, "using ..." or "typedef ..."; this used to work with versions <= 4.16.0 by assuming everything as a typedef. To fix the issue, check if "using " is found, otherwise fall back to considering that "typedef " was used. If not "typedef " is found in the definition, print a warning. Signed-off-by: Fabio Utzig <[email protected]>
Looks good to me. |
When using the @typedef <name> doxygen command, the generated XML does not have a proper definition, "using ..." or "typedef ..."; this used to work with versions <= 4.16.0 by assuming everything as a typedef. To fix the issue, check if "using " is found, otherwise fall back to considering that "typedef " was used. If not "typedef " is found in the definition, print a warning.
Fixes #534