Re: Result Set Cursor Patch

From: Brian Olson <bolson(at)bolson(dot)org>
To: <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Result Set Cursor Patch
Date: 2004-05-05 23:55:14
Message-ID: Pine.OSX.4.33.0405051645160.23295-100000@bolson.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

This outsider/new-guy-on-the-list thinks "4 space" tabs are great. I think
it's very portable because if a file is indented with all tabs then
someone can set their editor to render that however they like: 2, 4, 8, e,
Pi, etc. "spaces".

4 space + 8-space-tabs is the least portable. Everyone has to configure
their editor exactly alike.

all spaces is portable, everyone gets the same thing, but on the down
side, everyone gets the same thing.

Of course, that's just my opinion, I could be wrong.

Brian Olson
http://bolson.org/

On Thu, 6 May 2004, Oliver Jowett wrote:

> Also, now that the driver is separate from the main code tree, maybe
> it'd be a good idea when reindenting to use more "normal" (for java
> anyway) indentation rules -- e.g. use either all spaces or spaces and
> 8-character tabs when indenting. The current 4-character tabs rule is
> fairly unusual. That'd make driver editing easier across a range of
> IDEs; sure, I have my xemacs settings that play nicely with the current
> scheme, but it's a barrier to entry for anyone who hasn't worked on the
> driver before.

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Oliver Jowett 2004-05-06 00:02:58 V3 extended query protocol and type problems
Previous Message Oliver Jowett 2004-05-05 23:06:57 Re: Result Set Cursor Patch