Path: csiph.com!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.lang.forth
Subject: Re: multitasking vs multiple interpreters
Date: Tue, 12 Aug 2025 09:45:07 -0700
Organization: A noiseless patient Spider
Lines: 15
Message-ID: <87pld01obw.fsf@nightsong.com>
References: <871pq0uppw.fsf@nightsong.com> <2025Jul29.094901@mips.complang.tuwien.ac.at> <107d890$2nleq$1@dont-email.me> <2025Aug11.194958@mips.complang.tuwien.ac.at> <nnd$627ce76c$69ac11c6@67bbc40320ec651e>
MIME-Version: 1.0
Content-Type: text/plain
Injection-Date: Tue, 12 Aug 2025 16:45:08 +0000 (UTC)
Injection-Info: dont-email.me; posting-host="5b4bb2c463e8a80e554e76cf19feb783"; logging-data="3585549"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18jyZS/ASX+8JqrRDYbv43/"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
Cancel-Lock: sha1:goRvrDB2eFA07+NeQMoI6FbYLRU= sha1:PaIWMcYTGtwWb9u5iGnosC05vis=
Xref: csiph.com comp.lang.forth:134120

albert@spenarnc.xs4all.nl writes:
> The only essential difference between COT and PRE is that you must
> do PAUSE in COT. The other differences can be anything.

COT and PRE = cooperative and preemptive, idk if those are standard
abbreviations but ok.  One advantage of COT is that you don't have to
worry about critical sectons.  I think COT tends to get displaced by PRE
as systems get more complicated though.  COT is too easy to wedge if
some task blocks indefinitely.

> I don't think it makes sense to talk about COT in general, because
> the most important use case has disappeared, and there are no
> canonical examples any more.

What was the most important use case?