Re: Is the dangling else a syntax bug?

vbdis@aol.com (VBDis) writes:
> wclodius@aol.com (Wclodius) schreibt:
> The "appropriate" number of space characters (to be defined!) IMO
> makes tabs the better choice for indentation. One tab - one level of
> indentation.
>
> As you mentioned already, a system-wide definition for the tab width
> will cure possible problems in printing, and encourages all tools to
> use that user-definable value.


Perhaps but if you have multiple systems (code bases) which use
different tab widths then you have to keep flipping back and forth.
For example in my current project there is a combination of company
written and third party code that means there are 6 distinct C styles
and 3 different tab widths (2, 4, 8). Most of this can be programmed
around in a decent editor, though it would be much easier if there
were no tabs and so nothing to program around.


However as soon as the code escapes your environment then the problems
begin. For example, if you email it to someone, the only way they
know what the tab width is if you tell them for each file or group of
files what the width is. Similarly when you print the files you have
to be careful to tell the printer what the width is for each file or
group of files -- I have use shell script wrappers but I still
occasionally use the wrong one with disgusting results. Again it
would be simpler if there were no tabs.
[I think this argument is done now. -John]

Return to the comp.compilers page.
Search the comp.compilers archives again.