Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site mplvax.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!harvard!talcott!panda!genrad!decvax!ittatc!dcdwest!sdcsvax!sdcc3!mplvax!cdl
From: cdl@mplvax.UUCP (Carl Lowenstein)
Newsgroups: net.lang.c
Subject: Re: The legacy of FORTRAN
Message-ID: <202@mplvax.UUCP>
Date: Mon, 22-Jul-85 21:58:52 EDT
Article-I.D.: mplvax.202
Posted: Mon Jul 22 21:58:52 1985
Date-Received: Fri, 26-Jul-85 04:11:07 EDT
References: <11457@brl-tgr.ARPA> <68@ucbcad.UUCP> <505@scc.UUCP> <1021@ucbtopaz.CC.Berkeley.ARPA>
Reply-To: cdl@mplvax.UUCP (Carl Lowenstein)
Organization: Marine Physical Laborator of SIO at UCSD
Lines: 15

In article <1021@ucbtopaz.CC.Berkeley.ARPA> mwm@ucbtopaz.UUCP (Mike Meyer) writes:
>>Supposedly this is harder to understand.   In the book "Learning
>>to Program in C" by Thomas Plum he mentions that they looked
>>at a bunch of C code and found out that 90% of C programmers
>>use i and j as index variables.
>
>Which just goes to show that the FORTRAN integer type names will always be
>with us.

Mathematicians and physicists were using i and j as index variables
long before Fortran.  In fact, long before programmable digital computers.

-- 
	carl lowenstein		marine physical lab	u.c. san diego
	{ihnp4|decvax|akgua|dcdwest|ucbvax}	!sdcsvax!mplvax!cdl