Deutsch   English   Français   Italiano  
<86cyg73ezo.fsf@linuxsc.com>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.arch
Subject: Re: Stacks, was Segments
Date: Mon, 27 Jan 2025 17:26:51 -0800
Organization: A noiseless patient Spider
Lines: 33
Message-ID: <86cyg73ezo.fsf@linuxsc.com>
References: <vdlgl9$3kq50$2@dont-email.me> <vmbd4n$3v6su$3@paganini.bofh.team> <vmbi6u$3js5u$1@dont-email.me> <04876fc002ab019a74c78113a36622f3@www.novabbs.org> <vmf5vv$2cse$1@gal.iecc.com> <lv18qpFjhe9U1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Date: Tue, 28 Jan 2025 02:26:51 +0100 (CET)
Injection-Info: dont-email.me; posting-host="1612c1484c3aeea3b113b4fe0f3b985e";
	logging-data="1423392"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+Z4Ea1Qs6Nzi02NH52lHFN5xDb/qKimO4="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:ybNEh1SxKeRc17hR0RDiSlrSGTo=
	sha1:cPdT5YHtH/cbwrOKl9cEdifZy4s=
Bytes: 2602

Niklas Holsti <niklas.holsti@tidorum.invalid> writes:

> On 2025-01-18 5:08, John Levine wrote:
>
>> According to MitchAlsup1 <mitchalsup@aol.com>:
>>
>>>> Stacks are small because OS people make them small, not because of
>>>> a valid technical reason that has ever been explained to me.
>>>> "To avoid infinite recursion" is not a valid reason, IMHO.
>>>
>>> Algol 60 only had stack allocation for dynamically sized arrays,
>>> so stacks had to be as big as the data are.
>>
>> Huh?  Algol 60 routines could be mutually recursive so unless it was
>> a leaf procedure or the outer block, everything not declared "own"
>> went on the stack.
>
> Mitch's point AIUI was that Algol 60 had no heap allocation (and no
> explicit pointer types), so indeed all data were either on the stack
> or statically allocated.
>
> I'm not an English native speaker, but it seems to me that Mitch
> should have written "Algol 60 had only stack allocation" instead of
> "Algol 60 only had stack allocation".

Yes.  I have seen this situation described as a rule for "only" to
be put as late in the sentence as still make sense.

Putting on my editor hat, I would recommend revising the sentence
more thoroughly, as for example, "Algol 60 had no way of allocating
memory except by means local variables on the stack" (assuming that
is the case;  my memories of the rules of Algol may have undetected
ECC errors).