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 705649DC86A for ; Mon, 16 Jan 2006 14:51:49 -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 12945-03 for ; Mon, 16 Jan 2006 14:51:45 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 1CC349DC84E for ; Mon, 16 Jan 2006 14:51:40 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k0GIpc8c010962; Mon, 16 Jan 2006 13:51:38 -0500 (EST) To: Neil Conway cc: Andrew Dunstan , thomas@tada.se, pgsql-hackers@postgresql.org, jgardner@jonathangardner.net Subject: Re: source documentation tool doxygen In-reply-to: <1137436300.9145.78.camel@localhost.localdomain> References: <43CB85A8.9080001@tada.se> <38611.68.143.134.146.1137419873.squirrel@www.dunslane.net> <1137436300.9145.78.camel@localhost.localdomain> Comments: In-reply-to Neil Conway message dated "Mon, 16 Jan 2006 13:31:40 -0500" Date: Mon, 16 Jan 2006 13:51:38 -0500 Message-ID: <10961.1137437498@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.089 required=5 tests=[AWL=0.089] X-Spam-Score: 0.089 X-Spam-Level: X-Archive-Number: 200601/470 X-Sequence-Number: 78574 Neil Conway writes: > I don't think it would be all that painful. There would be no need to > convert the entire source tree to use proper Doxygen-style comments in > one fell swoop: individual files and modules can be converted whenever > anyone gets the inclination to do so. I don't think the maintenance > burden would be very substantial, either. In the previous go-round on this topic, I seem to recall some concern about side-effects, to wit reducing the readability of the comments for ordinary non-doxygen code browsing. I'd be quite against taking any noticeable hit in that direction. A quick look through the doxygen manual doesn't make it sound too invasive, but I am worried about how well it will coexist with pgindent. It seems both tools think they can dictate the meaning of the characters immediately after /* of a comment block. regards, tom lane