Horton

Re: [HACKERS] Source code format vote

D'Arcy Cain <darcy@druid.net>

View thread
From: darcy@druid.net (D'Arcy J.M. Cain)
To: vev@michvhf.com (Vince Vielhaber)
Cc: pgman@candle.pha.pa.us (Bruce Momjian), hannu@tm.ee (Hannu Krosing), lockhart@alumni.caltech.edu (Thomas Lockhart), pgsql-hackers@postgreSQL.org (PostgreSQL-development), wieck@debis.com (Jan Wieck)
Date: 2000-01-04T02:22:44Z
Lists: pgsql-hackers 
Thus spake Vince Vielhaber
> Ok, this is probably a really dumb question and probably even been answered
> before but I missed it.  Why not make a tab be a tab and however it appears
> in the end programmer's editor can be up to the programmer?  Or is pgindent
> changing tabs to spaces?

Not a dumb question at all.  However, think about comments.  Look at
this example.

	i++;	/* This variable is being incremented.  I am commenting *
			 * this because it is such a stupid variable name
			 */

Under my editor that comment lines up nicely but it will look cockeyed
for many people reading this because I used tabs instead of spaces and
my tabs are 4, not the usual 8.

-- 
D'Arcy J.M. Cain <darcy@{druid|vex}.net>   |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 425 1212     (DoD#0082)    (eNTP)   |  what's for dinner.