Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.lang.c Subject: Re: Python recompile Date: Fri, 14 Mar 2025 21:20:17 -0000 (UTC) Organization: A noiseless patient Spider Lines: 28 Message-ID: References: <20250309012626.00001276@yahoo.com> <20250310135828.116@kylheku.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Fri, 14 Mar 2025 22:20:18 +0100 (CET) Injection-Info: dont-email.me; posting-host="ee9c283082583b8b66572d63300a48c0"; logging-data="2213432"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+/Vbw20mdmAWb0nhGVFMPC" User-Agent: Pan/0.162 (Pokrosvk) Cancel-Lock: sha1:vyZjn/aDCf/pNATE31ldpNDpxRg= On Fri, 14 Mar 2025 12:46:21 -0700, Chris M. Thomasson wrote: > On 3/13/2025 6:48 PM, Lawrence D'Oliveiro wrote: > >> On Thu, 13 Mar 2025 16:45:28 -0700, Chris M. Thomasson wrote: >> >>> I have no idea how the Python dev's use IOCP with sockets. >> >> They can’t figure out a way to support file I/O notifiers (of the kind >> commonly used with event loops) with it. If you know of a way to do it, >> please tell us. > > Well, usually, iirc, been a while, when GQCSEX returns we take the > WSAOVERLAPPED and convert it to our extended structure. Basically > similar to how Linux uses offsetof to extend node structures, or on > Windows CONTAINING_RECORD, then we can use that to pass into a function > called on_read, on_write, on_accept, on_connect, ect... type of > functions. Does that require explicitly queuing a read or a write operation? According to the platform support notes , ProactorEventLoop does not allow the addition of reader/writer callbacks for caller-supplied file descriptors. Remember what these callbacks do: they notify that the FD will accept a read or a write, not that a pending read or write has completed.