On Sunday 09 December 2001 12:42 pm, Mike Orr wrote: > Regarding tabs vs spaces, I don't know, there's no one ideal answer. > Universal compatibility argues for using tabs--that is what the tab > key and \t are for anyway---with tabstops at 8 columns. On the other > hand, this encourages mixing tabs and spaces (tabs for the > indentation level, then a few more spaces to line up expression parts > vertically), which is way more trouble than it's worth. And if > somebody sets their tabstop to a different setting, there goes your > beautiful formatting (and possible syntax errors, or functions and > loops that end on the wrong line, if they indent their lines with all > spaces and then somebody else opens the file with a different > tabstpop/expandtabs setting and adds their own lines.
Most of these problems are tab-space mixture problems, which we don't allow. Clark seems to have run into some, so we'll run a check (just like we'd have to if we used all spaces and someone eventually ran into a tab). Formatting does not get skewed when tabs are used for indentation. On Sunday 09 December 2001 12:42 pm, Mike Orr wrote: > at the bottom of every file I edit frequently (as you'll see in some > Cheetah files). Yes, it sucks that you'd need a line like that for > every editor, but maybe it shows that the real culprit is that > editors don't have a common convention for specifying this. And it > sucks that you can't use the \t that was specifically designed for > this purpose, but that's the way the cookie crumbles. I wish editors would pick up a .foorc in the directory of the edited file. This would pay off much larger. -Chuck _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
