Reformat existing Doxygen comments
At least thread_mpi and non-bonded kernels in the current source tree contain some Doxygen comments. These should be modified to produce documentation more in line with the new module structure, possibly after moving these components away from the src/gromacs/gmxlib/ directory. Also, some of the things that appear under the Related Pages section in the generated documentation are not linked to from anywhere else.
Misc. Doxygen improvements.
- Excluded src/external/ from Doxygen documentation.
- Made inherited members appear in class documentation. Makes API
documentation easier to read if there are many public members
inherited from base classes.
- Added conditional sections for Doxygen that can be used in addition to
\internal and \libinternal.
- Consolidated use of \internal and \libinternal in file comments:
all installed (=public API) headers now produce some documentation for
the public API, even if the file only contains declarations that are
not directly in the public API.
- Added short file documentation for a few files where it was missing.
Gromacs wiki has also been updated with the changes.
Doxygen updates for fatalerror module.
Also some other misc. fixes.
Related to IssueIDs #662.
Removed unnecessary information from user API docs.
There are likely other places where \if or \cond Doxygen constructs
would be useful, but this is a start. More can be added when
documentation is further updated.
#2 Updated by Teemu Murtola almost 7 years ago
- Project changed from Source code reorganization to GROMACS
- Category set to documentation
- Target version set to 5.x
The code has changed a lot, and it needs a second look whether there are stray doxygen comments and what needs to be done to clean up the documentation. 4.6 has removed some of the comments mentioned in the description, but has also added new ones.
#4 Updated by Teemu Murtola over 6 years ago
- Status changed from New to Closed
- Target version set to 5.0
Most of the mentioned sections are no longer present or are not included in the generated documentation. The doc-check target checks at least the most obvious issues that produce messy documentation.
The original motivation for this issue is now resolved.