On Fri 22 Dec 2006 at 10:51:21 -0600, Matthew D. Fuller wrote:
> Just to be contrary, I find that to be just about the _worst_ possible
> style. I indent with tabs, and highly dislike indenting with spaces,
> but surely the worst of both worlds it indenting with *BOTH*. The
> code is then only remotely readable with an 8-char tabstop. With my
> standard 4-char tabstops, it only seems to indent every _other_ block.
> With a 2-char tabstop, it indents a long ways, then outdents a little,
> then indents another long ways, then outdents a little, then...
Let me explain. Tabs are historically 8 worth spaces. There is too much
text based on that to ever be able to change that. However, an indent of
4 (often) looks better. Therefore many programmer's editors (including
Vim, Emacs, even MS Visual Studio) can dynamically mix tabs and spaces
such that indents are 4 and tabs are 8 (using tabs at the start of the
line and possibly 4 extra spaces after them). Unfortunately this is
indeed going to look bad if you set tabs to 4, but then so is a lot of
other text. Of course, we could ban tabs and always use spaces, but
that will need a lot of reminding people I expect.
A partial solution might be to use tabs only for indentation and nowhere
else. It would foil any other lining up that people might want to do
though.
> Related, tabs for alignment (e.g. on the variable declarations at the
> top of the function) are IMAO the wrong place to use tabs as well.
Most of this stuff can easily be reformatted with the "indent" program.
It has more options than ls to select all these things.
> (I don't care for K&R braces, or for spaces between function names and
> args either, but those are more minor details)
As long as the braces aren't the ugly GNU style, half-indented! Eew!
while
{
something;
}
some more...
> Matthew Fuller (MF4839) | [EMAIL PROTECTED]
-Olaf.
--
___ Olaf 'Rhialto' Seibert -- You author it, and I'll reader it.
\X/ rhialto/at/xs4all.nl -- Cetero censeo "authored" delendum esse.
