-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Trying to document function named "i_calloc()" produces unwanted links #10735
Comments
Based on the given, incomplete, example it is not possible to tell what the problem might be, so
|
I could not create a smaller example in order to recreate the issue, so here is the (slightly changed) complete project. It is relatively small, I hope this is not an inconvenience. The function that seems to create the problem is located in file: You can generate the documentation by cd-ing to There already exist two versions of the documentation, one that is correct (with i_calloc doc deactivated, folder You can go to "Module Index" > "Allocators" in the documentation to visit the page describing the allocators. I am using the latest version of Doxygen: 1.10.0 (ebc57c6) on Ubuntu Linux 22.04 (wsl) Hope this helps, let me know if you need additional info. |
Bisecting gave the following result (9a8b3da ):
|
That is correct. Basically in the "false" case, false links are created for keywords like "void", "static", "default" as well as for argument names. This happens not only in the "Allocators" page, but throughout the entire documentation. I thought it was a matter of naming convention that caused this behavior, hence the "i_calloc" reference, but maybe it is something else as i did some name changing and the problem persisted. |
Another thing i noticed (do not know if it is relevant) : |
When trying to document the following function:
Doxygen produces false links that point to this function.
Nearly all function arguments as well as C++ keywords are mapped to this.
Looks like doxygen creates a bunch of these:
This happens only for
i_calloc()
and NOT fori_malloc()
.It also does NOT happen for the templated version of
i_calloc()
:The text was updated successfully, but these errors were encountered: