This needs a follow-up poll on the right way to indent code:
[ ] 8 unit wide hard tabs only [ ] 4 unit wide hard tabs only [ ] space-based soft tabs at 8 units only [ ] space-based soft tabs at 4 units only [ ] an ungodly mixture of 8 unit wide hard tabs and spaces [ ] whatever M-x c-indent-command thinks is right [ ] I only write lisp
A Brief, Incomplete ... History of Programming Languages (http://james-iry.blogspot.com/2009/05/brief-incomplete-and-mostly-wrong.html) "1940s - Various "computers" are "programmed" using direct wiring and switches. Engineers do this in order to avoid the tabs vs spaces debate."
(And I still think sticking to at least not often going much over 80 helps more than it reduces readability. But I'll settle for 132 as a hard limit.)
I think unless it's obviously insane, it doesn't matter too much as long as everyone does the same thing (or everyone does something that can be munged into the same thing by the VCS). I once found a piece of code that variously used 2, 3, 4, 5, 6, and 8 spaces for indenting. That was fun to understand.
(no subject)
Date: 2009-05-11 07:06 pm (UTC)[ ] 8 unit wide hard tabs only
[ ] 4 unit wide hard tabs only
[ ] space-based soft tabs at 8 units only
[ ] space-based soft tabs at 4 units only
[ ] an ungodly mixture of 8 unit wide hard tabs and spaces
[ ] whatever M-x c-indent-command thinks is right
[ ] I only write lisp
(no subject)
Date: 2009-05-11 07:47 pm (UTC)(no subject)
Date: 2009-05-11 09:58 pm (UTC)"1940s - Various "computers" are "programmed" using direct wiring and switches. Engineers do this in order to avoid the tabs vs spaces debate."
(And I still think sticking to at least not often going much over 80 helps more than it reduces readability. But I'll settle for 132 as a hard limit.)
(no subject)
Date: 2009-05-11 10:07 pm (UTC)(no subject)
Date: 2009-05-12 11:42 am (UTC)(no subject)
Date: 2009-05-12 12:00 pm (UTC)