-
Notifications
You must be signed in to change notification settings - Fork 342
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
Parsable markup documentation with doxygen #491
Conversation
abaf676
to
1abad34
Compare
Enforcing the documentation comments with YCM can get very profitable. See the GetDocs command. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doxygen looks interesting and since the work required to make it work is minimal we can give it ago.
I pointed out some small nitpicks and I also think Doxyfile
should be in docs/internal
let's not mix user docs with developer docs.
HACKING.md
Outdated
- Use `@param` to describe all input parameters | ||
- Documentation comments should start with a double star (`/**`) | ||
- Look forward to properly link all member types | ||
- Functions with an appended `()` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These 2 lines needs some more explanation, I can't make much sense of them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added an example and also the way to reference symbols/variables.
HACKING.md
Outdated
- Add comments to all functions and methods | ||
- Markdown inside the comments is allowed and also desired | ||
- Add the comments to the prototype. Doxygen will merge the protoype and implementation documentation anyways. | ||
Except for **static** methods. Add the documentation header to the implementation and *not to the prototype*. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That period is going to confuse people comma would be more appropriate here.
b9db3de
to
d7d94dc
Compare
Parsable markup documentation with doxygen
This is a start to have the documentation with doxygen, which also contains markup to be able to compile it at the end of the day.
With this, one's able to compile a document to get an overview of the internal structures of dunst.
I've moved my own comments of the
queues.c
andlog.c
files to be compliant.