Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have some large, mostly procedural codes that need to be well documented. This generally involves repeated use of a number of functions that must be executed in a certain order.
Doxygen is a great product, but it seems very oriented towards documenting OOP codes. Does anyone have any tips on how to use doxygen in a natural way to document procedural work?
There’s nothing inherently OOP about the way doxygen works. It’s just able to extract more information about OO code because it has more information in it (e.g., inheritance graphs).
We use doxygen for plain C code and it works just as well, minus the information that plain C doesn’t provide when compared to C++. Just use doxygen’s grouping (@addtogroup et al) features to organize the generated documentation and you’re good to do.