Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site hcrvax.UUCP
Path: utzoo!hcrvax!jims
From: jims@hcrvax.UUCP (Jim Sullivan)
Newsgroups: net.lang.c
Subject: Re: The legacy of FORTRAN
Message-ID: <1889@hcrvax.UUCP>
Date: Mon, 22-Jul-85 14:24:36 EDT
Article-I.D.: hcrvax.1889
Posted: Mon Jul 22 14:24:36 1985
Date-Received: Tue, 23-Jul-85 04:28:24 EDT
References: <11457@brl-tgr.ARPA> <68@ucbcad.UUCP> <505@scc.UUCP> <1021@ucbtopaz.CC.Berkeley.ARPA>
Organization: Human Computing Resources, Toronto
Lines: 18

>>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.

Why FORTRAN and not mathematics ?  As I remember my math, i, j, and k are 
generally index variables, a, b, and c are constants; m and n are array
bounds; etc. etc.

The fact the 90% of C programmers use i and j as index variables is not
a particularly stunning fact, it's like saying most programs have at
least one if statement.

Jim