All I know is that the major advantage of tabs is that they reduce source size, beyond that they make a lot of things difficult.
For instance your editor groks mixed tabs/spaces and interconverts on indent/outdent as appropriate. But my editor either uses a tab or uses some number of spaces, and for reasons unknown decides that the appropriate place to insert its "indent string" is at the front of the line. End result? When I try to outdent your code it doesnt work properly, as 4 spaces + a tab is visually the same thing as a single table when the tab is defined to be 8 chars long. Which it has to be if you are working with code that comes from editors that do the evil tab/space thing.
I routine encounter this problem, and I routinely mutter about it, as often the perl patch pumpkings convert my space indented code back to tab indented code before the apply the patch, so even my own code mysteriously ends up having fucked indenting properties in my editor when i go to change stuff. Necessitating me to convert the code back to spaces, blah blah.
Even worse is when you work with people whose idea is to change the size of a tab, which is just a nightmare when people on your team all have different ideas on how big it should be. Inevitably people use spaces instead of tabs _sometimes_ and then you end up with indenting problems.
So I'd say that in the interest of maximum interoperability and minimum hassle use spaces instead.
In reply to Re: Tabs vs Spaces lets give this a go
by demerphq
in thread Tabs vs Spaces lets give this a go
by EvanCarroll
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |