Sujet : Re: Python recompile
De : chris.m.thomasson.1 (at) *nospam* gmail.com (Chris M. Thomasson)
Groupes : comp.lang.cDate : 13. Mar 2025, 06:50:56
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vqtro1$33l9c$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
User-Agent : Mozilla Thunderbird
On 3/10/2025 2:55 PM, Kaz Kylheku wrote:
On 2025-03-10, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:
On 3/10/2025 2:36 PM, Lawrence D'Oliveiro wrote:
On Mon, 10 Mar 2025 15:20:00 +0200, Michael S wrote:
>
Similar to poll(), yes. Not so similar to super-ugly select(). I
hope that Unix people stopped using select in new programs two or
more decades ago.
>
Seems like WaitForMultipleObjects is more similar to select() than
poll(), though: it has a fixed limit (MAXIMUM_WAIT_OBJECTS) on the
number of objects you can wait on at once.
>
But WaitForMultipleObjects can do things that poll can not, like
waiting on semaphore or on event or on thread (for completion, which
POSIX people, in their eternal fondness for idiotic names call
'join').
>
[...]
>
For some damn reason I am remembering that the array that
WaitForMultipleObjects waits on should be "shifted" or even randomized
per call in a server loop that is using EVENTS. IIRC, this was way back
in late 90's and early 2000's.
You remember correctly. I remember coding this.
[...]
I tried to email you back but it got kicked back.
Re: Python recompile
Re: Python recompile