[OT] Auto code reformating / one coding style enforcment.

[Jarrett Billingsley]

"Sean Kelly" <sean at f4.ca> wrote in message 
news:ebq7gr$2ski$1 at digitaldaemon.com...

> Hard tabs work okay for leading indentation, but for inner 
> indentation--long function calls, if statements, variable lists, etc--they 
> can render code unreadable if viewed with a different tab width.

Oh I never, ever use tabs in internal indentation for that very reason. 
Then again, I rarely internally indent my code.

> Even worse is if in a group project, some people use hard tabs and others 
> spaces, and those using hard tabs have different tab widths. I've worked 
> on projects like this (including the one I'm on now) and the tabs are a 
> disaster.

Sounds like a reason to have a group coding style.

> Given the relative ease with which modern editors can jump from word to 
> word and eat whitespace, I simply don't understand the attachment to hard 
> tabs.

I don't like being able to select the individual spaces in the indentation, 
or being able to accidentally get the indentation off by a space or two 
through odd editing.  And not all editors are created equal in the cursoring 
respect - some can go thru spaces as if they were tabs; some depend on 
global settings to determine if that happens; and some don't offer it at 
all.  With tabs, there's no other way to cursor through them.