| Deutsch English Français Italiano | 
| <vqcnd0$32tgb$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article | 
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Richard Harnden <richard.nospam@gmail.invalid>
Newsgroups: comp.lang.c
Subject: Re: Which code style do you prefer the most?
Date: Thu, 6 Mar 2025 17:52:32 +0000
Organization: A noiseless patient Spider
Lines: 30
Message-ID: <vqcnd0$32tgb$1@dont-email.me>
References: <vpkmq0$21php$1@dont-email.me> <vq785i$1u7v7$1@dont-email.me>
 <20250304101022.154@kylheku.com> <vq7shq$226p3$1@dont-email.me>
 <vq7u5u$21gol$2@dont-email.me>
 <20250305152224.ea400cb92445c78f6a4ba523@g{oogle}mail.com>
 <vq9kf0$2efj9$1@dont-email.me> <vq9mkb$2erto$1@dont-email.me>
 <20250305183051.3cca469a0fd757595152b261@g{oogle}mail.com>
 <vq9uqh$2g9q3$1@dont-email.me> <vqa0gr$2gmc7$1@dont-email.me>
 <vqa1rq$2gr5h$1@dont-email.me> <Ea0yP.6763$SVG3.6427@fx42.iad>
 <vqbptn$2triu$1@dont-email.me> <WBiyP.170259$BrX.10828@fx12.iad>
Reply-To: nospam.harnden@invalid.com
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 06 Mar 2025 18:52:33 +0100 (CET)
Injection-Info: dont-email.me; posting-host="f279196d502bbe371caf7fe4f777ad38";
	logging-data="3241483"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19jmjOYZ8XqihQg/+0kMRHr3V76cz1ooeU="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:83PzOw+qeV0i7poYwwGijHR3kX4=
Content-Language: en-GB
In-Reply-To: <WBiyP.170259$BrX.10828@fx12.iad>
Bytes: 2500
On 06/03/2025 14:49, Scott Lurndal wrote:
> David Brown <david.brown@hesbynett.no> writes:
>> On 05/03/2025 18:51, Scott Lurndal wrote:
>>> Richard Harnden <richard.nospam@gmail.invalid> writes:
>>>> On 05/03/2025 17:09, Janis Papanagnou wrote:
>>>>> On 05.03.2025 17:40, bart wrote:
>>>>>> [...]
>>>
>>>>
>>>> Seriously, short variable names for common things - i, j, k for loop
>>>> counters;
>>>
>>> So, one might ask _why_ i, j, k instead of a, b, c?
>>>
>>> Answer: Fortran IMPLICIT INTEGER
>>>
>>
>> Nonsense.
>>
>> Ask rather why Fortran picked i, j, k for integer-type index variables.
>> Their use for that function in maths /long/ predates Fortran.
> 
> That doesn't mean that C programmers didn't adopt the
> use of i,j,k from FORTRAN.
I'd always assumed it was because 'index' was too much to type, and that 
j and k just followed on.
Didn't know about any hysterical raisins.