Re: Python recompile

On Tue, 11 Mar 2025 14:12:45 GMT
scott@slp53.sl.home (Scott Lurndal) wibbled:

Muttley@DastardlyHQ.org writes:

On Mon, 10 Mar 2025 17:12:06 GMT
scott@slp53.sl.home (Scott Lurndal) wibbled:

Muttley@DastardlyHQ.org writes:

On Mon, 10 Mar 2025 15:20:00 +0200
Michael S <already5chosen@yahoo.com> wibbled:

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.

>
Nothing wrong with select if you're not multiplexing hundreds of file
descriptors. Does the job.
>

>
The primary constraint for select(2) is not the _number_ of files
that can be selected amongst (although that _is_ a constraint),
but rather the largest file descriptor number is limited by the
select(2) bitmap interface (FD_SETSIZE not only defines the number
of file descriptors that can be passed, but also the highest
valued file descriptor that can be passed).  poll(2) has no
such limits.

>
File descriptors get reused on every version of *nix I've ever programmed
on so unless you have hundreds of descriptors open at any one time thats not
going to be a problem.

>
$ man dup2
>
There are very few reasons to favor select over poll in new code.

Theres one very big one in that with select you don't have to manage a
pollfd array. With poll you either have to hardcode its size and then do
[something] if you have too many descriptors, or piss about with realloc()
nonsense. For a simple client that maybe only has stdout and a socket open
I'd choose select() every single time.