Re: source documentation tool doxygen - Mailing list pgsql-hackers

From Michael Glaesemann
Subject Re: source documentation tool doxygen
Date
Msg-id D8B9412A-E682-42D6-BB93-AF92A6BCE255@myrealbox.com
Whole thread Raw
In response to Re: source documentation tool doxygen  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: source documentation tool doxygen  (Joachim Wieland <joe@mcknight.de>)
List pgsql-hackers
On Jan 17, 2006, at 3:51 , Tom Lane wrote:

> 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.

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.

Michael Glaesemann
grzm myrealbox com





pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: Anyone see a need for BTItem/HashItem?
Next
From: Tom Lane
Date:
Subject: Re: ScanKey representation for RowCompare index conditions