Re: OT - trivial programming language
- To: debian-user@lists.debian.org
- Subject: Re: OT - trivial programming language
- From: Kai Grossjohann <kai@emptydomain.de>
- Date: Fri, 04 Jun 2004 09:32:57 +0200
- Message-id: <[🔎] 864qprg4ly.fsf@rumba.de.uu.net>
- References: <40B7768A.1060506@yahoo.com> <slrncbevh3.ihj.spam@home.bounceswoosh.org> <20040528193224.GA10350@infidel.spots.ab.ca> <20040529020850.GD8662@luna.mooo.com> <slrncbfubu.mae.spam@home.bounceswoosh.org> <20040529173154.GK8662@luna.mooo.com> <40B8E781.4040604@dmiyu.org> <20040529214630.GB28241@luna.mooo.com> <40B91C3A.1090603@dmiyu.org> <slrncbilu1.shs.spam@home.bounceswoosh.org> <[🔎] 20040601190227.GB8822@dman13.dyndns.org>
Derrick 'dman' Hudson <dman@dman13.dyndns.org> writes:
> If tabs and spaces are combined for indentation purposes, then when
> you change your tab display width you will see a horrid mess of
> incorrectly indented code.
This is often, but not always the case. I explained how tabs and
spaces are combined so that changing the tab display width will avoid
a horrid mess of incorrectly indented code.
To wit, consider this piece of code, based on tab width = 4:
for(;;) {
if (a == b) {
some_long_function_name(a,
b);
}
}
I used spaces only in this message, please pretend that my style of
mixing tabs and spaces was used. Changing tab display width to 8
will then produce this:
for(;;) {
if (a == b) {
some_long_function_name(a,
b);
}
}
Changing it to 2 will produce this:
for(;;) {
if (a == b) {
some_long_function_name(a,
b);
}
}
Now, you may like some of them better than others, but clearly none of
them is a mess. Each of them looks as you would expect from the
tab width setting.
Kai
Reply to: