Re: Manipulating C code at the AST level, in C
Richard Kettlewell <[email protected]>
| Newsgroups | comp.os.linux.misc |
|---|---|
| Organization | terraraq NNTP server |
| Message-ID | <[email protected]> |
c186282 <[email protected]> writes: > On 8/14/26 07:26, Nuno Silva wrote: >> The online manual here (a GNU/Linux system) says: >> "poll, ppoll - wait for some event on a file descriptor" >> >> Perhaps that should be rewritten. Reading further, it's not singular, >> but that description with "*A* file descriptor" does make it sound >> like poll is not a suitable replacement for select. https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/CONTRIBUTING > Polling, for this sort of thing, has to be > fast and constant - a big CPU drag. poll() doesn’t poll, despite the name. > You are basically WAITING for something to happen - which MAY or may > NOT happen at any moment. > > The writers of various utils and basic system functions NEED to > include some kind of easy flag or interrupt routine that other utils > can monitor at VERY LOW CPU/Time investment. Already done, several decades ago. -- https://www.greenend.org.uk/rjk/