> Bzzt! Thanks for playing, but tabs are evil and must be destroyed.
> Your own reasoning shows the problem - your tabs may not be the same
> as my tabs. Most serious Unix developers use the One True Tab Setting
> (every 8 positions), so your solution involving indentation by tabs
> only makes the code much too wide, and it is often impossible to
> neatly line things up without using spaces. I personally prefer a
> two-character indent for Perl code, and most C programmers
> I know ident blocks by 8 and continued expressions by 4. And we all
> hate code that wraps off the edge of the screen. It's just not
> realistically possible to have people with different tab settings
> work on the same code. One has to learn to adapt to other people's
> style when morking on their code, even if it's personally annoying.
You're making my point for me. Tabs are a single character that gets
displayed according to how you set your editor preferences. If you want to
see a tab set to 2-chars wide, you set it to chars wide. I can set it to 5
chars or whatever I want to see. The source code doesn't change.
(what, did you really think a tab put 8 spaces in the file? duh.)
For a multi-developer project, it is very important to pick a style
> and enforce it consistently, but that's for Tucows to do internally.
> I think they're much better off using spaces than even saying "thou
> shalt use 8-character tabs".
No... tab settings are specific to the editor. In the file, it's just a tab.
1 character. How it displays a preference of the user.
> After all, there may be a few people
> with obscure minority operating systems like AmigaDOS, Windows and
> MacOS trying to look at the code.
Exactly. You have again made my point.
Can we please implement a moron filter on this list?
--
Joe Rhett Chief Technology Officer
[EMAIL PROTECTED] ISite Services, Inc.
PGP keys and contact information: http://www.noc.isite.net/Staff/
