| From: | "Brendan Jurd" <direvus(at)gmail(dot)com> |
|---|---|
| To: | "Bruce Momjian" <bruce(at)momjian(dot)us> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: A small rant about coding style for backend functions |
| Date: | 2007-11-07 14:36:07 |
| Message-ID: | 37ed240d0711070636y7b1ebfc3rad89099932155f92@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/8/07, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> The problem is that a full list would be harder to understand than just
> looking at the existing code and following it, or taking suggestions
> from us as we review the patch.
>
What makes you say it would be necessarily harder to understand? That
seems strange to me. Isn't that a bit like saying that the Postgres
developers' FAQ is harder to understand than just asking the question
on -hackers?
What I'm talking about isn't weird. Large collaborative projects
often have style guides. To take an example, Python has one for C
code [1] and another for Python code [2]. They are clear, useful and
easy to understand.
[1] http://www.python.org/dev/peps/pep-0007/
[2] http://www.python.org/dev/peps/pep-0008/
Regards,
BJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2007-11-07 15:40:36 | Re: Weird type selection choice |
| Previous Message | Bruce Momjian | 2007-11-07 13:48:36 | Re: Segmentation fault using digest from pg_crypto |