Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!oddjob!gargoyle!ihnp4!homxb!mtuxo!mtune!codas!usfvax2!ateng!chip
From: chip@ateng.UUCP (Chip Salzenberg)
Newsgroups: comp.lang.c
Subject: Re: documentation standards........
Message-ID: <54@ateng.UUCP>
Date: Wed, 21-Oct-87 17:27:04 EST
Article-I.D.: ateng.54
Posted: Wed Oct 21 17:27:04 1987
Date-Received: Sun, 25-Oct-87 02:32:16 EST
References: <9710@brl-adm.ARPA> <1596@megatest.UUCP> <1987Oct15.212022.20550@sq.uucp>
Reply-To: chip@ateng.UUCP (Chip Salzenberg)
Organization: A.T. Engineering, Tampa, FL
Lines: 19

I can't resist...

In article <1987Oct15.212022.20550@sq.uucp> msb@sq.UUCP (Mark Brader) writes:
>
>2.  The examples show several signs that they were not written by a C
>    programmer; for instance, using a while-loop instead of
>
>       for (iterations = 0; upper - lower > epsilon; iterations++)

It is _not_ true that a "C programmer" will use a "for" loop whenever
possible.  For example, I consider myself a fairly experienced C
programmer, and my personal rule is that only variables involved in loop
_control_ should appear in the for statement.

-- 
Chip Salzenberg         "chip@ateng.UUCP"  or  "{uunet,usfvax2}!ateng!chip"
A.T. Engineering        My employer's opinions are not mine, but these are.
   "Gentlemen, your work today has been outstanding.  I intend to recommend
   you all for promotion -- in whatever fleet we end up serving."   - JTK