![]() ![]() I can even make a list: * * item 1 * * item 2 * * item 3 * * \param a this is one input parameter * \param b this is another * \param c and this is the output * * \author L. In my projects, I create a doxygen. PREDEFINED DOXYGEN1 EXPANDASDEFINED noname. * I could add many more details here if I chose to do so. In any event, to fix this issue, Ive used a Doxygen Trick: Make sure you have a DOXYGEN predefined and expand the noname macro. The manual also states: Warning: When you have a very large class hierarchy where many classes derive from a common base class, the resulting image may become too big to. The Doxygen way, putting comments before the class or function definition in this case double hash characters are used to start the documentation block, and then a single hash character can be. I wasnt able to find a graph, like the one you are looking for, in that list. The Pythonic way, using 'docstrings', that is, a block of text surrounded by triple quotes immediately after the class or function definition. In languages where you define all your variables must be declared at the beginning. Just give it a proper name or document it 'in source': Cat cats // holds a bunch of cats. However, as you are programming in C (++), it should not be a problem to document local variables in source. - /*! \brief Example function * * \details **myfunction()** takes a and b as arguments and miraculously creates c. The doxygen manual for graphs and diagrams lists, which kind of graphs could be created. Here is a list of all functions, variables, defines, enums, and typedefs with links to the files they belong to: application : index.php GLOBALS . You shouldnt use doxygen to document your implementation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |