-
Notifications
You must be signed in to change notification settings - Fork 483
New c-mode Doxygen function documentation using Javadoc style tags. #264
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
Conversation
|
This looks exactly like this one apart from the fact that there is a \ instead of @. |
|
It is exactly the same as the one you referenced because I used that one as the template. The original version uses the Doxygen style "\xxx" commands. My snippet uses the Javadoc style "@xxx" command which is also valid Doxygen command: Specifically, I was working on a C project, which is why it went into the c-mode snippets directory. I haven't tested it with C++ project. Is there a better location in the snippet tree for this so that it works for C/C++ projects? Also, I'm happy to change the expansion key to something more suitable if you have any suggestions? |
|
There is |
|
I'll test your suggestion and update accordingly. Thanks.
|
c-lang-common so that the snippet will be available for both c & c++ programs.
|
I moved the file to |
|
I'm a bit confused now @dpitic And why would you want to use the Java convention if you were working on a C/C++ project anyway? |
|
My snippet uses the Javadoc style comment "@" which is valid Doxygen. It can be used to document any programming language. It's just a matter of style preference. Doxygen parses it identically to "\" in order to generate documentation. IDEs made by Jetbrains, Netbeans, Eclipse, and text editors like Sublime Text use this Doxygen documentation block to show function and other symbol documentation in the editor. So, considering the fact that this is general Doxygen function block documentation that can be used for any language, is there a more appropriate location in the snippet tree where it should go? |
|
@AndreaCrotti I've updated the I want to add an assembly language snippet. Should I do that in another branch in this fork, or create a new fork and pull request for that? |
|
@AndreaCrotti if you're still unsure about the It's good to have both styles to cater for people with different preferences. |
use. Added new nasm Doxygen function block document snippet.
|
Yes ok the current snippets we have don't have a great key either so maybe I can clean them up later on. |
New Javadoc style tag Doxygen function documentation block for C functions.