Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.arch
Subject: Re: Continuations
Date: Tue, 16 Jul 2024 01:09:58 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 18
Message-ID: <v74h95$un01$6@dont-email.me>
References: <v6tbki$3g9rg$1@dont-email.me> <v71jfh$jko$1@gal.iecc.com>
	<lfldplF1kmoU1@mid.individual.net> <v74cn9$tuk4$2@dont-email.me>
	<v74cug$t8j$2@gal.iecc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 16 Jul 2024 03:09:58 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="55f74b4ae2f116c131f41dc172ef4daf";
	logging-data="1006593"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19X57h16g7OigN+6G6PRSGh"
User-Agent: Pan/0.158 (Avdiivka; )
Cancel-Lock: sha1:DUqepqhMbBzYxYMLU9J/2v/LUOA=
Bytes: 1805

On Mon, 15 Jul 2024 23:56:00 -0000 (UTC), John Levine wrote:

> According to Lawrence D'Oliveiro  <ldo@nz.invalid>:
>>On Mon, 15 Jul 2024 23:06:13 +0300, Niklas Holsti wrote:
>>
>>> IMO, for something to qualify as a continuation-passing call, the
>>> caller should select the callee -- the thing to be executed next --
>>> but in SAGE/SABRE it is the scheduler that selects what to execute
>>> next.
>>
>> What you have is that SAGE/SABRE has built a higher-level scheduler
>> abstraction on top of lower-level coroutines/continuations.
> 
> It was an event loop, not coroutines.

The one does not preclude the other. So they lacked the coroutine 
abstraction; that could have been added easily enough in the application 
implementation language.