| From: | darcy(at)druid(dot)net (D'Arcy J(dot)M(dot) Cain) |
|---|---|
| To: | vev(at)michvhf(dot)com (Vince Vielhaber) |
| Cc: | pgman(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian), hannu(at)tm(dot)ee (Hannu Krosing), lockhart(at)alumni(dot)caltech(dot)edu (Thomas Lockhart), pgsql-hackers(at)postgreSQL(dot)org (PostgreSQL-development), wieck(at)debis(dot)com (Jan Wieck) |
| Subject: | Re: [HACKERS] Source code format vote |
| Date: | 2000-01-04 02:22:44 |
| Message-ID: | m125JcS-000AUUC@druid.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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(at){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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 2000-01-04 02:35:49 | Re: [HACKERS] Source code format vote |
| Previous Message | D'Arcy J.M. Cain | 2000-01-04 02:18:47 | Re: [HACKERS] Source code format vote |