On Oct 6, 2011, at 12:49 PM, Krzysztof Kosiński wrote:
So the effort is part of the overall work to have diagrams, charts, maps of where to find what, etc., that will be exactly what newcomers need. And I should also be able to get some templates, guidelines, etc. to help the rest of us gain maximum use with minimal effort.
Also completely unrelated to what you've been actually doing. These things would be valuable, and I'm all for you doing them, but removing forward headers and @brief is at best unnecessary and at worst counterproductive.
Oh, no. It's not unrelated at all.
For many years now I've used doxygen to generate overviews of projects to discover the structure. I need to get good up to date structure docs done on our codebase. Without clean comments it's difficult to get doxygen to give its best output. And without good doxygen output it is harder to be able to see and document the structure.
Also, to be counter productive, the @brief tags would really have to add something to the documentation. From my experience getting doxygen and such adopted at different companies, I've only ever seen @brief get in the way, and not help.