Deutsch English Français Italiano |
<vbj7ni$1qat7$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!weretis.net!feeder8.news.weretis.net!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: Sun, 8 Sep 2024 06:04:00 +0200 Organization: A noiseless patient Spider Lines: 35 Message-ID: <vbj7ni$1qat7$1@dont-email.me> References: <v66eci$2qeee$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> <87ikxconq4.fsf@bsb.me.uk> <v6n8iu$24af0$1@dont-email.me> <20240711115418.00001cdf@yahoo.com> <v6oamt$2d8nn$1@dont-email.me> <v6oct4$2djgq$2@dont-email.me> <v6of96$2ekb0$1@dont-email.me> <v6ovfc$2hcpf$1@dont-email.me> <v6p4hf$2icph$1@dont-email.me> <v6qgpu$2t6p7$3@dont-email.me> <v6r33m$30grj$1@dont-email.me> <v6r3iv$30gru$1@dont-email.me> <20240712045301.394@kylheku.com> <87sewesg89.fsf@nosuchdomain.example.com> <865xresvxz.fsf@linuxsc.com> <87h6ay3jaz.fsf@nosuchdomain.example.com> <87mskqtip3.fsf@bsb.me.uk> <87cyll3dk2.fsf@nosuchdomain.example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Injection-Date: Sun, 08 Sep 2024 06:04:02 +0200 (CEST) Injection-Info: dont-email.me; posting-host="7c62bf7f846a95dba5faec77c27ae61c"; logging-data="1911719"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/WXmAqG3fRLhIQi8iHe9/g" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 Cancel-Lock: sha1:pADlDmiHhvgN6e8aRNrBsG5iyWA= In-Reply-To: <87cyll3dk2.fsf@nosuchdomain.example.com> Bytes: 3361 On 03.09.2024 00:18, Keith Thompson wrote: > Ben Bacarisse <ben@bsb.me.uk> writes: >> Keith Thompson <Keith.S.Thompson+u@gmail.com> writes: > [...] >>> I'm mildly disappointed. Since arguments are *passed* and >>> functions/procedures are *called*, surely it would have made more sense >>> to use "pass by value" rather than "call by value", especially in a >>> language where the mechanism can vary per parameter. >> >> All that is, I think, due to subsequent changes in (English) language >> use. In Algol 60, procedures were invoked and /parameters/ were called >> by value or name. Maybe the term was intended to reflect the idea that >> the code in the body "called for the value" of the parameter. >> >> The word "call" now refers, almost universally, to invoking a function >> or procedure. As a result, the idea of "calling a parameter" reads >> oddly, but at the time I'm sure it seemed perfectly reasonable. > > I just searched the Algol 60 report for all occurrences of the word > "call". It does refer to both procedures and parameters being "called", > but parameters are only "called by value" or "called by name", never > just "called". > > It's difficult to tell what the idiomatic usage would have been at the > time. Indeed. Maybe we need to consider some more context information about that time. I've read that Algol 60 adopted the parameter passing principles from the lambda-calculus; value parameters and name parameters. (I haven't searched for respective documents.) Janis