In message <[EMAIL PROTECTED]>, Alexander Leidinger writes: >Quoting "Poul-Henning Kamp" <[EMAIL PROTECTED]> (Fri, 26 May 2006 20:20:36 >+0200): > >> In message <[EMAIL PROTECTED]>, Alexander Leiding >> er writes: >> >> > This is the kernel subsystem API documentation generation framework. >> > >> > It uses doxygen to generate the API documentation. For each subsystem >> > a very small (about 20 lines with comments) subsystem specific Doxyfile >> > has to be written (have a look at the README for more). All common doxygen >> > options are specified in a separate file. >> >> Now, this is all well and good, but the most critical question in >> my mind is: how do we prevent (or alternatively: mark up) documentation >> for functions which are not supposed to be public ? > >http://www.stack.nl/~dimitri/doxygen/commands.html#cmdinternal
Can we agree that no functions will be put into publicized documentation until somebody has considered if the function actually is a public function or not ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[EMAIL PROTECTED]"
