Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.lang.c Subject: Re: Python recompile Date: Sat, 15 Mar 2025 02:31:55 -0000 (UTC) Organization: A noiseless patient Spider Lines: 9 Message-ID: References: <20250310135828.116@kylheku.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Sat, 15 Mar 2025 03:31:56 +0100 (CET) Injection-Info: dont-email.me; posting-host="7c9322988cd10723f336ea9799d3e4e4"; logging-data="2674397"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19CRdJcS3lnJ2iemk1sCJv5" User-Agent: Pan/0.162 (Pokrosvk) Cancel-Lock: sha1:uSV7pt/DnXF4FpnS/drBhmcrGUI= Bytes: 2285 On Fri, 14 Mar 2025 16:29:34 -0700, Chris M. Thomasson wrote: > There is a way to tell IOCP to do a so-called "zero byte > receive" where it does not use any non-paged memory for the receive > buffer because it's zero. Then when IOCP completes it means you are > guaranteed a non-blocking receive call, pretty nice! Not sure why you need such a roundabout trick just to get a nonblocking version of an I/O call.