Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ncsu.UUCP
Path: utzoo!watmath!clyde!akgua!mcnc!ncsu!jcz
From: jcz@ncsu.UUCP (John Carl Zeigler)
Newsgroups: net.lang.c
Subject: Re: C parsing : Significance of spaces
Message-ID: <2573@ncsu.UUCP>
Date: Sat, 28-Apr-84 20:11:20 EDT
Article-I.D.: ncsu.2573
Posted: Sat Apr 28 20:11:20 1984
Date-Received: Sun, 29-Apr-84 09:15:40 EDT
References: <5794@mcvax.UUCP>
Organization: N.C. State University, Raleigh
Lines: 26

>

	Blaming the programmer vs. blaming C for
things like "a/*b" begs the question.   If you are good at your
job and take care writing code that is clean and
managible, then you wont have problems like "a/*b".

If you understand how the tools you use work, then you should
see something like "a/*b" as soon as you type it.

Of course, there is the occasional typo,  but that is not
what we are talking about.

If the tools you use enable you to produce better code, then they
are good tools.  If they do not make it easier to produce good code,
then they are bad tools.    I would list C in the former group
because it does allow you to produce good code (by any standard -
readibility, efficiency; perhaps not orthagonally).

The only caveat is that you must have a lot of experience
with C to really know how to take advantage of these things.


John Carl Zeigler
North Carolina State University