Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!husc6!spdcc!ima!haddock!karl
From: karl@haddock.ima.isc.com (Karl Heuer)
Newsgroups: comp.lang.c
Subject: Re: C preprocessing
Message-ID: <18102@haddock.ima.isc.com>
Date: 22 Sep 90 00:22:26 GMT
References: <59770@iuvax.cs.indiana.edu>
Reply-To: karl@kelp.ima.isc.com (Karl Heuer)
Organization: Interactive Systems, Cambridge, MA 02138-5302
Lines: 15

In article <59770@iuvax.cs.indiana.edu> bomgard@iuvax.cs.indiana.edu (Tim Bomgardner) writes:
>Wouldn't it be nice, if ... the compiler would do what I meant [by
>interpreting the indentation] instead of what I said?

I personally like the idea, but it's not C (nor any other language I use,
though I understand Occam has it).  So, being realistic, let's say instead:

Wouldn't it be nice if the compiler (or some related tool) would provide
(optional!) warnings for possibly misindented code?

Things to worry about: (a) whitespace caused by macro expansion; (b) how to
count tabs vs. spaces; (c) accepting all plausible personal indentation styles
(or making it user-configurable).

Karl W. Z. Heuer (karl@kelp.ima.isc.com or ima!kelp!karl), The Walking Lint