Skip to content
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

generate C++ "typedef" documentation #10836

Open
paule32 opened this issue Apr 29, 2024 · 2 comments
Open

generate C++ "typedef" documentation #10836

paule32 opened this issue Apr 29, 2024 · 2 comments
Labels
C/C++ needinfo reported bug is incomplete, please add additional info

Comments

@paule32
Copy link
Contributor

paule32 commented Apr 29, 2024

Hello,
I can document typedef objects, but I can not document the keyword "typedef"
How can I do this ?

@doxygen
Copy link
Owner

doxygen commented Apr 29, 2024

Why would you want to do this?
Can you please attach a self-contained example (zip with source + config file) that shows the problem?

@doxygen doxygen added the needinfo reported bug is incomplete, please add additional info label Apr 29, 2024
@paule32
Copy link
Contributor Author

paule32 commented Apr 30, 2024

I would make a documentation about the C/C++ programming language.
And as such, there a core keywords like void, for, if, else, while, typedef, ...
They would be handled as keywords by doxygen, but I can not link against documentation.
As example:
I have source code in doxygen rendered html like \code{.cpp} - these paragraphs will be color highlighted.
But the keywords can not be link-followed to a topic page.
Or on the list where the members are listed - there will be the same.
I could std::string make clickable by import a .cc file, where the namespace std, and the class string exists.
Keywords are not namespaces - so, how could I documenting it ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C/C++ needinfo reported bug is incomplete, please add additional info
Projects
None yet
Development

No branches or pull requests

3 participants