Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connections
Warning: mysqli::query(): Couldn't fetch mysqli in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\index.php on line 66
Article <v146ts$vrsv$9@dont-email.me>
Deutsch   English   Français   Italiano  
<v146ts$vrsv$9@dont-email.me>

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

Path: ...!2.eu.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.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.lang.c++,comp.lang.c
Subject: Re: Threads across programming languages
Date: Sat, 4 May 2024 02:35:40 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 14
Message-ID: <v146ts$vrsv$9@dont-email.me>
References: <GIL-20240429161553@ram.dialup.fu-berlin.de>
	<RPidnQT6TOLEU7L7nZ2dnZfqnPWdnZ2d@giganews.com>
	<RsudnRRDUtiEcbL7nZ2dnZfqnPednZ2d@giganews.com>
	<gmWdnYejrq5snq77nZ2dnZfqn_GdnZ2d@giganews.com>
	<v0vd0a$3n0k7$3@dont-email.me>
	<v0vt1v$3qlsf$1@raubtier-asyl.eternal-september.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 04 May 2024 04:35:40 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="3e71a75fbbcf81b4a78150d90a6a33ff";
	logging-data="1044383"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18HEmVIIpauVT6ISNnU8aDr"
User-Agent: Pan/0.155 (Kherson; fc5a80b8)
Cancel-Lock: sha1:4lwLB0ayldekQIpNGWy2ca7a1tQ=
Bytes: 1891

On Thu, 2 May 2024 13:22:39 +0200, Bonita Montero wrote:

> Am 02.05.2024 um 08:48 schrieb Lawrence D'Oliveiro:
>>
>> The normal, non-comedy way of handling this is to have the task await
>> something variously called a “future” or “promise”: when that object is
>> marked as completed, then the task is automatically woken again to
>> fulfil its purpose.
> 
> The problem with a future and a promise is that in most languages you
> can't wait for multiple futures at once to have out of order completion.

Of course you can. Any decent event-loop framework will provide this 
capability. Python’s asyncio does. I use it all the time.