Path: ...!news.nobody.at!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Janis Papanagnou <janis_papanagnou+ng@hotmail.com>
Newsgroups: comp.lang.c
Subject: =?UTF-8?Q?Re:_technology_discussion_=e2=86=92_does_the_world_need_a?=
 =?UTF-8?Q?_=22new=22_C_=3f?=
Date: Sat, 13 Jul 2024 11:46:34 +0200
Organization: A noiseless patient Spider
Lines: 41
Message-ID: <v6tidr$3hj4d$1@dont-email.me>
References: <v66eci$2qeee$1@dont-email.me> <v6joi4$1epoj$1@dont-email.me>
 <871q42qy33.fsf@bsb.me.uk> <v6k6i0$1h4d3$1@dont-email.me>
 <87ed82p28y.fsf@bsb.me.uk> <v6m03l$1tf05$1@dont-email.me>
 <87r0c1nzjj.fsf@bsb.me.uk> <v6m716$1urj4$1@dont-email.me>
 <86ikxd8czu.fsf@linuxsc.com> <v6mggd$20g3f$1@dont-email.me>
 <20240710213910.00000afd@yahoo.com> <v6mm02$21cpb$1@dont-email.me>
 <865xtc87yo.fsf@linuxsc.com> <v6ol14$2fdrj$1@dont-email.me>
 <87msmnu5e3.fsf@nosuchdomain.example.com> <v6pdcf$2jijk$1@dont-email.me>
 <87frsfu0yp.fsf@nosuchdomain.example.com> <v6pfqj$2jijk$3@dont-email.me>
 <v6r4um$30q95$1@dont-email.me> <v6rcr5$320pj$1@dont-email.me>
 <v6spc7$3dlhs$1@dont-email.me> <87cynirl7d.fsf@nosuchdomain.example.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Injection-Date: Sat, 13 Jul 2024 11:46:36 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="14a5f16314952812b50a35483011f6fa";
	logging-data="3722381"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18kwcW0Sai5brW+FgdE3+Kp"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
Cancel-Lock: sha1:O4dwnLTQfRjKpXx/et7zaL9RvrA=
X-Enigmail-Draft-Status: N1110
In-Reply-To: <87cynirl7d.fsf@nosuchdomain.example.com>
Bytes: 3277

On 13.07.2024 06:04, Keith Thompson wrote:
> Janis Papanagnou <janis_papanagnou+ng@hotmail.com> writes:
>> On 12.07.2024 15:59, bart wrote:
> [...]
>>> So how are the elements of the caller's array accessed?
>>>
>>> No copies have been supplied to the caller. So access is by ... ?
>>
>> ...by an implicit pointer value dereferentiation and a global
>> access to the pointed to storage area.
> 
> A small quibble: I suggest "indirect" would be clearer than "global".

I used the term "indirection" before a an abstract description
of the common superset of the function that "references" and
"pointers" provide.

But, yes. Global is not a good word. (It itches me as well.)

Here I wanted to include (in a subtle way) another aspect (that
had already been mentioned before by others, granted); that the
change through indirection is not bound to some sort of "local"
parameter object (an array passed as parameter by value), but as
pointer may point just to (and manipulate) any "global" data.

> 
> For example, a function can define a local array object and use
> its name as an argument in a call to another function.
> 
> [...]
> 
>> As an end point to the discussion (just for some recreational
>> reading) I suggest "The Development of the C Language" by D.
>> Ritchie.
> 
> Available at <https://www.bell-labs.com/usr/dmr/www/chist.pdf>.

Thanks for the link. (I had only a local copy of it.)

Janis