Skip site navigation (1) Skip section navigation (2)

Postgresql coding conventions

From: Abbas <abbas(dot)butt(at)enterprisedb(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Postgresql coding conventions
Date: 2008-09-11 09:26:05
Message-ID: 1221125165.5637.12.camel@abbas-laptop (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
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?



pgsql-hackers by date

Next:From: Simon RiggsDate: 2008-09-11 10:04:23
Subject: Re: Transaction Snapshots and Hot Standby
Previous:From: Hannu KrosingDate: 2008-09-11 08:38:21
Subject: Re: Transaction Snapshots and Hot Standby

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group