This is a good way to see what's been marked up, but might not be the right approach in the long run. At the moment we're instructing Doxygen to document all functions, whether they have proper comment markup or not.Doxygen reports filename conflicts in a few cases where it can't work out which of several files to use. We probably should be marking header files with the names by which we include them (eg, "dns/resolver.h"). Our use of \file is wrong in many places.Instead, we attempt to use Doxygen's native facilities wherever possible, on the assumption that we'll add new features later as we need them but should start as simply as we can. We don't try to generate the list of files to document on the fly. We don't attempt to use Doxygen as a wrapper framework for other documentation (eg, ISC Tech Notes, the ARM. We don't generate fancy extra Doxygen tags files from the RFC database.
#Doxygen list all functions manual
In a major departure from previous attempts to use Doxygen with BIND9, this manual attempts to take the simplest approach to every choice Doxygen gives us.Known issues with our current use of Doxygen: See the Doxygen web site for more information about Doxygen, including its manual.See the tabs at the top of the screen to navigate through the generated documentation.See the files in doc/doxygen for the source to this page and the Doxygen configuration that generates the rest of the manual.This is the beginning of an internals manual for BIND9.
0 kommentar(er)
