On Tue, Jan 17, 2006 at 12:15:02AM -0500, Tom Lane wrote:
> The thing seems to have only the very vaguest grasp on whether it is
> parsing C or C++ ... or should I say that it is convinced it is parsing
> C++ despite all evidence to the contrary? I'd be happier with the
> pretty pictures if they h
Bruce Momjian writes:
> Wow, looks great. Is that URL stable? Can we link to it from the
> PostgreSQL developers page?
The thing seems to have only the very vaguest grasp on whether it is
parsing C or C++ ... or should I say that it is convinced it is parsing
C++ despite all evidence to the con
On Monday 16 January 2006 10:51, Tom Lane wrote:
> Neil Conway <[EMAIL PROTECTED]> 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 con
Wow, looks great. Is that URL stable? Can we link to it from the
PostgreSQL developers page?
http://www.postgresql.org/developer/coding
---
Joachim Wieland wrote:
> I've created a browsable source tree "documentat
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 sty
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 b
Neil Conway <[EMAIL PROTECTED]> 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
On Mon, 2006-01-16 at 07:57 -0600, Andrew Dunstan wrote:
> I too have done this. But retrofitting Doxygen style comments to the
> PostgreSQL source code would be a big undertaking. Maintaining it, which
> would be another task for reviewers/committers, would also be a pain unless
> there were some
Andrew,
Why not publish it as it stands today? Changing comments can be done in due time, no need to
rush it. Or are the comments in some special format today that is used by some other tool?
What I'm trying to say is that for people like me, this would be very useful. Just clicking
on a struc
Thomas Hallgren said:
> I wish I've had this when I started working with PostgreSQL. This looks
> really good. Very useful indeed, even without the comments. What kind
> of changes are needed in order to get the comments in?
>
I too have done this. But retrofitting Doxygen style comments to the
Try following the link (the Doxygen icon) - it has both a tutorial and
extensive doc.
Regards,
Kim Bisgaard
Thomas Hallgren wrote:
I wish I've had this when I started working with PostgreSQL. This
looks really good. Very useful indeed, even without the comments. What
kind of changes are neede
I wish I've had this when I started working with PostgreSQL. This looks really good. Very
useful indeed, even without the comments. What kind of changes are needed in order to get
the comments in?
Regards,
Thomas Hallgren
Joachim Wieland wrote:
I've created a browsable source tree "documentat
12 matches
Mail list logo
