Xref: utzoo comp.lang.misc:7757 comp.lang.c:39069
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!udel!haven.umd.edu!socrates.umd.edu!socrates!rockwell
From: rockwell@socrates.umd.edu (Raul Rockwell)
Newsgroups: comp.lang.misc,comp.lang.c
Subject: Re: About the variable 'I' (was Re: long names (was Readability of Ada))
Message-ID: <ROCKWELL.91May7082834@socrates.umd.edu>
Date: 7 May 91 13:28:34 GMT
References: <3878@ssc-bee.ssc-vax.UUCP> <jls.672366979@rutabaga> <12394@dog.ee.lbl.gov>
	<1991Apr26.034205.27308@netcom.COM>
	<1991May7.052930.6170@tkou02.enet.dec.com>
Sender: rockwell@socrates.umd.edu (Raul Rockwell)
Followup-To: comp.lang.c
Organization: Traveller
Lines: 16
In-Reply-To: diamond@jit533.swstokyo.dec.com's message of Tue, 7 May 1991 05: 29:30 GMT

Morgan Schweers:
   >    As for the person who screamed about 'C' programmers using 'i'
   >in for loops, I've found that it makes it Real Clear(tm) that that
   >is nothing more than an incremental loop counter.

Norman Diamond:
   If you use a more descriptive name, then the loop can say WHAT it's
   counting and thereby ease the burden on "countless" maintenance
   programmers.

Seems to me that WHAT it's counting is best determined by looking at
where the loop starts and stops.  (Unless maybe you've got a
tremendously large loop body, and the loop header is going to be
several pages back from where you use the counter.)

Raul Rockwell