X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 111C69DC875 for ; Mon, 16 Jan 2006 19:04:43 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 64649-05 for ; Mon, 16 Jan 2006 19:04:42 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from ns2.rox.net (emma.rox.net [212.63.65.11]) by postgresql.org (Postfix) with ESMTP id DB1109DC851 for ; Mon, 16 Jan 2006 19:04:37 -0400 (AST) Received: from localhost ([127.0.0.1]) by emma.rox.net with esmtp (Exim 4.52) id 1EydOz-0003lv-UF; Tue, 17 Jan 2006 00:04:41 +0100 Received: from [87.223.172.248] (helo=mcknight.kawo2.rwth-aachen.de) by emma.rox.net with esmtpa (Exim 4.52) id 1EydOz-0003k9-5p; Tue, 17 Jan 2006 00:04:41 +0100 Received: by mcknight.kawo2.rwth-aachen.de (Postfix, from userid 1000) id F1B264681AE; Tue, 17 Jan 2006 00:04:19 +0100 (CET) Date: Tue, 17 Jan 2006 00:04:19 +0100 From: Joachim Wieland To: Michael Glaesemann Cc: Tom Lane , Neil Conway , Andrew Dunstan , thomas@tada.se, pgsql-hackers@postgresql.org, jgardner@jonathangardner.net Subject: Re: source documentation tool doxygen Message-ID: <20060116230419.GA2524@mcknight.de> References: <43CB85A8.9080001@tada.se> <38611.68.143.134.146.1137419873.squirrel@www.dunslane.net> <1137436300.9145.78.camel@localhost.localdomain> <10961.1137437498@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: X-Operating-System: Linux 2.6.13.4 on an i686 User-Agent: Mutt/1.5.9i Content-Transfer-Encoding: quoted-printable X-Scanned-By: rockenstein AG X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.102 required=5 tests=[AWL=0.102] X-Spam-Score: 0.102 X-Spam-Level: X-Archive-Number: 200601/494 X-Sequence-Number: 78598 On Tue, Jan 17, 2006 at 06:51:15AM +0900, Michael Glaesemann wrote: > I haven't looked at it yet, but might there not be a way to have a > preprocessing step where the current comment format is converted to > something doxygen-friendly? pg_indent2doxygen or something? Then the > current comment style could be maintained and doxygen could get what > it likes. It's not about getting in all the comments, it's mostly about comments describing functions / makros / typedefs / structures / global variables and the like. Comments in function bodies will just stay I guess. However we could try to find some de facto rules about comments to get mo= st of the matches: For example a comment starting on column 0 of the line is probably one you're looking for vs. one that has some whitespace at the beginning is not. Of course this would still need manual review for every file. Joachim --=20 Joachim Wieland joe@mcknight= .de C/ Usandizaga 12 1=B0B ICQ: 372= 25940 20002 Donostia / San Sebastian (Spain) GPG key availa= ble