Re: Postgresql coding conventions - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Postgresql coding conventions
Date
Msg-id 48C8EF18.8080207@dunslane.net
Whole thread Raw
In response to Postgresql coding conventions  (Abbas <abbas.butt@enterprisedb.com>)
List pgsql-hackers

Abbas wrote:
> 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?
>
>
>   

I don't think we have a standard. If there is to be one I'll cast as 
many votes as possible for the use of underscores. 
readingWithoutSpacesReallySucks.

cheers

andrew


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: [Review] pgbench duration option
Next
From: Simon Riggs
Date:
Subject: Re: Transaction Snapshots and Hot Standby