Reputation: 517
The company I'm working for does not use Doxygen, and in their coding standard explicitly prohibits "parseable comment styles such as javadoc, etc".
However, I've still found it very useful to run Doxygen myself just so I can see the class structure, and get nice per-class documentation of all the methods the a class has, including inherited ones.
The company does document the classes in the header files, with simple comments above each method declaration. It would be very useful if I could configure Doxygen to treat these comments as the function descriptions, even though they don't start with any Doxygen markers.
So: is it possible to get Doxygen to treat comments on the line above declarations as if they are the description for that item even when the comment is not marked with Doxygen's "parse this comment" markers?
The next best thing is to click on the #include <foo.h>
links at the top of the class file to jump to the file itself, which I have been using. That doesn't help for seeing all of a derived class's methods in one place, though.
Upvotes: 0
Views: 101
Reputation: 9047
When the comments above the methods have only "normal" comments i.e. with /*
or //
the best thing to do would be that you write a small filter (see e.g. INPUT_FILTER
with sed
or awk
or ... ) in which you convert (all?) /*
/ //
comments into /**
/ ///
so the comment blocks are parsed by doxygen. The result is not as nice as with "full" doxygen comments.
It is just a workaround and can lead to unexpected results when the INPUT_FILTER
does not exclude e.g. //
inside strings from consideration.
Upvotes: 1