| From: | Larry Rosenman <ler(at)lerctr(dot)org> |
|---|---|
| To: | PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | coding style guidelines? |
| Date: | 2000-11-16 17:17:58 |
| Message-ID: | 20001116111758.A28449@lerami.lerctr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Is there any guidelines on the formatting of the C code in
PG? As I was working on guc-file.l yesterday, I noticed
some things with LONG lines (I broke some of them up).
I was wondering if there were formal standards?
Also, do we care about extraneous #include's?
(src/backend/parser/scansup.c has #include <ctype.h> which it
doesn't need on closer inspection, for example).
When I copied scansup.c into guc-file.l I added the #include
<ctype.h>, but it may not need it.
Larry
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 (voice) Internet: ler(at)lerctr(dot)org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2000-11-16 17:24:38 | Re: [rfc] new CREATE FUNCTION (and more) |
| Previous Message | Thomas Lockhart | 2000-11-16 17:06:10 | Re: [HACKERS] Re: DBD::Pg installation seems to fail with 7.1 libs |