Basic support for reading documentation #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
qmfrederik
force-pushed
the
features/documentation
branch
from
1e02d13 to
2eaa12e
Compare
|
I've rebased this on top of master, so the merge conflicts should be gone now. |
|
Hi please check out the recent commits.. Seems there is no way to retrieve the original comment string and only Doxygen style comments can be retrieved. |
GordenOu
force-pushed
the
master
branch
4 times, most recently
from
69692a6 to
08420ae
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds very basic support for parsing comments/documentation (the
CXCommentstruct). It implements what I needed to parse documentation on enums, functions,...