C> comfortable with it. That being said, I don't see why the whitespace
C> considered such a radical change.
This is crucial in ensuring everybody's code LOOKS similar.
The whitespace construct makes a great positive difference in a team of
programmers who work on the same code.
The first thing I do when I open *anybodyies* C code in vim is to type
0vG==, which is goto line 0, visual highlight/selection, go to end of
file, and == auto-indents everything as it should be.
Unfortunately, if I end up making an improvement I need to submit back
to the author, I have to re-write those portions a 2nd time, using
THEIR styling, only in the lines effected. Otherwise the patch would be
for nearly the entire file.
But, if it weren't for this feature, I'm not sure I would even get so
far, I have a very difficult time dealing with the many different
tabs/spaces/mixed/unused/unconcerned that goes on there. Its great if
you're a preprocessor to simply skip all whitespace, its terrible for
the human mind to see an indentation that doesn't belong (not actually
a block), or miss a logical block statement because it wasn't indented
at all. Or to have to try tio figure out wether the author's tabstops
are 2, 4, 3, or 8 spaces, as some lines of code seem to line up while
others don't, especially when they get artsy fartsy about lining up all
of their multi-line statements beneath subsequent ('s and so on ...
---
■ [TN11.1] Archaic Binary
|
