Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 May 2006 20:44:57 +0200
From:      Alexander Leidinger <netchild@FreeBSD.org>
To:        "Poul-Henning Kamp" <phk@phk.freebsd.dk>
Cc:        cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: src/sys/doc/subsys Dependencies Doxyfile-cam Doxyfile-crypto Doxyfile-dev_pci Doxyfile-dev_sound Doxyfile-dev_usb Doxyfile-geom Doxyfile-i4b Doxyfile-kern Doxyfile-libkern Doxyfile-linux Doxyfile-net80211 ...
Message-ID:  <20060526204457.3e545e4f@Magellan.Leidinger.net>
In-Reply-To: <10526.1148667636@critter.freebsd.dk>
References:  <200605261806.k4QI67D3007680@repoman.freebsd.org> <10526.1148667636@critter.freebsd.dk>

next in thread | previous in thread | raw e-mail | index | archive | help
Quoting "Poul-Henning Kamp" <phk@phk.freebsd.dk> (Fri, 26 May 2006 20:20:36 +0200):

> In message <200605261806.k4QI67D3007680@repoman.freebsd.org>, 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

Bye,
Alexander.

-- 
Selling GoodYear Eagle F1 235/40ZR18, 2x 4mm + 2x 5mm, ~150 EUR
you have to pick it up between Germany/Saarland and Luxembourg/Capellen
http://www.Leidinger.net    Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org       netchild @ FreeBSD.org  : PGP ID = 72077137



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060526204457.3e545e4f>