Re: [feature request] Doxygen comments for parser files
Andre Noll <[email protected]>
| Newsgroups | gmane.comp.gnu.gengetopt.general |
|---|---|
| Message-ID | <[email protected]> |
On 14:31, Lorenzo Bettini wrote: > so you wouldn't comment static functions, right? Yes, I don't use doxygen comments for static functions. If something in a static function needs commenting, I use the "usual" comments instead, these are ignored by doxygen. But of course that's only my personal taste. OTOH, there's also the EXTRACT_STATIC option of doxygen that skips static functions entirely when set to "NO", so they don't show up anywhere, documented or not. > and for the main parser functions, would it be better to be commented on > the .h file or in the .c file? AFAIK doxygen doesn't care. I prefer the .c file because I can look at the code while writing the documentation. That's probably irrelevant for automatically generated comments though ;) > Moreover, the few times I used doxygen, I used to use the @param and > @return (as in javadoc), while from the sources on paraslash it looks > like \param and \return should be used? Both variants are possible, there's no difference in functionality. Doxygen is well documented, btw: http://www.stack.nl/~dimitri/doxygen/manual.html Regards Andre -- The only person who always got his work done by Friday was Robinson Crusoe _______________________________________________ Help-gengetopt mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-gengetopt
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGeSTGWto1QDEAkw8RAn8qAKCiqq37o7kngqDRINPs2Aq0/NqPJgCgjcCT EBGeFZMn3R6jYpF0dF4iQfQ= =en+m -----END PGP SIGNATURE-----