This documentation is generated using Sphinx and Doxygen The two softwares are bridged by means of the Breathe extension The online version of this documentation is built and served by Read The Docs. The webpage http://pcmsolver.readthedocs.org/ is updated on each push to the public GitHub repository.
How and what to document¶
Doxygen enables documenting the code in the source code files thus removing a
“barrier” for developers. To avoid that the code degenerates into a Big Ball
of Mud, it is mandatory to document directly within the source code classes and
functions. To document general programming principles, design choices,
maintenance etc. you can create a .rst file in the
doc directory. Remember
to refer the new file inside the
index.rst file (it won’t be parsed
otherwise). Sphing uses reStructuredText and Markdown. Support for Markdown is not
as extensive as for reStructuredText, see these comments Follow the guidelines
in [WAB+14] regarding what to document.
Documeting methods in derived classes¶
Virtual methods should only be documented in the base classes.
This avoids unnecessary verbosity and conforms to the principle: “Document
_what_, not _how_” [WAB+14]
If you feel the _how_ needs to be explicitly documented, add some notes in the
How does this work?¶
To have an offline version of the documentation just issue
make doc in the
build directory. The HTML will be stored in
doc/html. Open the
doc/html/index.html file with your browser to see and browse the
Building the documentation requires Doxygen, Sphinx, Perl and the Python modules PyYAML, Breathe and Matplotlib.