Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Kaz Kylheku <643-408-1753@kylheku.com>
Newsgroups: comp.lang.c
Subject: Re: Python recompile
Date: Sun, 9 Mar 2025 18:06:18 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 34
Message-ID: <20250309110035.182@kylheku.com>
References: <vq1qas$j22$1@gallifrey.nk.ca> <vq3oag$18iv6$1@dont-email.me>
 <vq4hf2$1brf7$1@dont-email.me> <vq4l3d$1ck9e$1@dont-email.me>
 <vq4m0u$1ctpn$1@dont-email.me> <vq4n05$1d5dv$1@dont-email.me>
 <vq4om7$1dbo2$2@dont-email.me> <vq6dqh$1pskk$1@dont-email.me>
 <vq6f8p$1pmnk$1@dont-email.me> <vq6gqc$1qcp8$1@dont-email.me>
 <vq6ips$1pmnk$2@dont-email.me> <vq6j5h$1qosf$1@dont-email.me>
 <20250304092827.708@kylheku.com> <vq7g1p$1vmg5$1@dont-email.me>
 <vq94dt$2boso$1@dont-email.me> <vqcsk7$23bfo$1@paganini.bofh.team>
 <vqefn1$3flpt$1@dont-email.me> <vqeu5c$3imil$1@dont-email.me>
 <vqeun4$3iqbq$1@dont-email.me> <vqfcbe$3lkkc$1@dont-email.me>
 <871pv861ht.fsf@nosuchdomain.example.com>
 <20250308192940.00001351@yahoo.com> <vqi1ge$8jg8$1@dont-email.me>
 <vqibt3$ahu0$3@dont-email.me> <vqiibq$bq1o$7@dont-email.me>
 <20250309012626.00001276@yahoo.com> <vqiugc$dv5o$2@dont-email.me>
 <20250309112807.0000489d@yahoo.com>
Injection-Date: Sun, 09 Mar 2025 19:06:18 +0100 (CET)
Injection-Info: dont-email.me; posting-host="aa2b1c041ebb8b94f514b3b1a0062f8c";
	logging-data="905121"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18thYbHiPDhHKYep2MoC4NqPTWjFsCvFtg="
User-Agent: slrn/pre1.0.4-9 (Linux)
Cancel-Lock: sha1:BFQI/a1q4KWGQL5Zy28bfhzyGq0=
Bytes: 2853

On 2025-03-09, Michael S <already5chosen@yahoo.com> wrote:
> select/poll is the one way to do event-driven programming.
> There are other ways.

There are other ways, sure.

But the program you're trying to build uses poll, and not other ways.

So if that Just Works (tm), you don't have to do a darn thing
to the program.

Get it?

> In particular, under Windows you can
> simultaneously wait for multiple objects with API that is called...
> Surprise! WaitForMultipleObjects.

Does that still have a shitty limit of 64 handles?

Taking a program which polls on pipes and making it compile and work
with WFMO is not fun.

> If it's not enough, I would guess that if one wants ultimate
> scalability, one can force named pipes into working with I/O completion
> ports, which is as scalable as one could wish.

Personal scalability is most important; not blowing all your
evenings for the next three weeks porting some POSIX thing to
native Win32.

-- 
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca