![]() I wanted to document user testing procedures as close as possible to their corresponding unit tests or groups of unit tests. I remembered coming across this question when I was looking for a similar solution. (I'm currently working on doing something similar to get Doxygen to nicely document Google Tests, also in the context of a project for a highly-regulated industry.) These are hacks, and you'd have to fiddle around with Doxygen quite a bit to get it to handle this case nicely, but I hope these suggestions help somewhat. dox documentation in the source code documentation (or vice-versa). You can use various Doxygen commands to link back to the documentation of the actual source code, and you can also insert a copy of the. dox files would contain documentation generated from corresponding. dox files from your code before calling doxygen. Write a "Doxygen runner" that would automatically generate.(One odd behavior I dislike is that the \code command seems to strip leading spaces, so you wouldn't get indentation to work correctly.) I'm not sure where Doxygen would put these comments or how they'd look they might be pretty ugly, unfortunately. Then write a filter (see FILTER_PATTERNS) to replace this string with \code \endcode where is the next line of code that the filter sees. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |