Re: [HACKERS] Source code format vote

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] Source code format vote
Date: 2000-01-03 23:00:50
Message-ID: 38712A22.6C9F711B@tm.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
> Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
> > Was "spaces instead of tabs" one of the voted-on options? That would
> > make the tab issue moot, and would result in consistant appearance not
> > matter what tab setting one is using.
>
> Quite a good thought, actually. It'd be worth checking to see if there
> is any material expansion in the source's disk footprint and/or the
> size of a compressed tarball after getting rid of tabs entirely.
> I'd be willing to vote for this if the space penalty is not large...

Me too!

And, there already is an utility to entab/detab in tools section, so people
can use it if they absolutely must have tabs in their source.

AFAIK most decent editors also can [en/de]tab the source they are editing.

So my vote would be 4-space indents, no tabs

--------------
Hannu

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2000-01-03 23:18:54 Re: [HACKERS] Source code format vote
Previous Message Hannu Krosing 2000-01-03 22:56:46 Re: [HACKERS] Inprise/Borland releasing Interbase as Open source