Postgresql coding conventions - Mailing list pgsql-hackers

From Abbas
Subject Postgresql coding conventions
Date
Msg-id 1221125165.5637.12.camel@abbas-laptop
Whole thread Raw
Responses Re: Postgresql coding conventions  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Re: Postgresql coding conventions  (Andrew Dunstan <andrew@dunslane.net>)
Re: Postgresql coding conventions  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Hi,
I have noticed two different coding conventions being followed in
postgres code base.

See e.g. function names in syslogger.c

static void set_next_rotation_time(void);
static void sigHupHandler(SIGNAL_ARGS);

and variable names in the same file

int    bytes_in_logbuffer = 0;
char    *currentLogDir;

Chapter 46 of the documentation does not say much about variable or
function naming.

While writing code or reviewing a path are we supposed to consider the
camel cased names correct or the under-score separated names correct?

Regards
Abbas
www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Hannu Krosing
Date:
Subject: Re: Transaction Snapshots and Hot Standby
Next
From: Simon Riggs
Date:
Subject: Re: Transaction Snapshots and Hot Standby