I strongly disagree - it only takes some simple formatting rules.
I do it all the time, in fact, I'll even accept a challenge to
break any line > 80 into lines < 80, without obfuscation. Almost
always this leads to more understandable code.
Personally I prefer 2 spaces, but I can live with anything.
Using tabs is just plain convenient for me.
> Printing the Source with current excessive indentation is quite
> hopeless.
Agreed - but as a programmer I of course have a wide printer.
On narrow printers, you need to get out a magnifying glass,
and put the printer into a smaller pitch :-(
> Apparently the Great White Leader uses _only_ X with _wide_ window
> and has access to fine wide lineprinters.
I've mentioned this in the past, heck I started a thread like this
once - Linus finally added his formatting ideas to the docs.
Although I agree with Linus in most things, I disagree with the
free-formating of the source - not just spaces vs tabs either.
I'd like people to learn about alphabetical and numerical ordering
too, along with naming conventions, etc.
Don't even get me started on Linux's so called "self documenting code"....
-- Andrew E. Mileski mailto:aem@ott.hookup.net Linux Plug-and-Play Kernel Project http://www.redhat.com/linux-info/pnp/ XFree86 Matrox Team http://www.bf.rmit.edu.au/~ajv/xf86-matrox.html PGP Public keys are available from http://www.redhat.com/~aem/pgp-keys.txt