Re: Manipulating C code at the AST level, in C

From	The Natural Philosopher <tnp@invalid.invalid>
Newsgroups	comp.os.linux.misc
Subject	Re: Manipulating C code at the AST level, in C
Date	2026-08-15 11:33 +0100
Organization	A little, after lunch
Message-ID	<115pfae$3a5ei$3@dont-email.me> (permalink)
References	(19 earlier) <87h5l1so79.fsf@safunu.org> <115do8s$3i42e$2@dont-email.me> <115mu22$2evoe$4@dont-email.me> <nACdnfS17rW7fOL3nZ2dnZfqnPudnZ2d@giganews.com> <neaiapFpk4lU4@mid.individual.net>

Show all headers | View raw

On 15/08/2026 08:20, rbowman wrote:
> On Fri, 14 Aug 2026 23:47:19 -0400, c186282 wrote:
> 
>>     Polling, for this sort of thing, has to be
>>     fast and constant - a big CPU drag. You are
>>     basically WAITING for something to happen -
>>     which MAY or may NOT happen at any moment.
> 
> I used select() rather than poll() but I'm archaic. Typically the select
> call was in the main loop. The timeout was often 1 second. If the call
> returned a ready fd you took care of business. If it timed out, then you
> did whatever housekeeping was necessary, making sure it wasn't a long
> process.
> 
> Without the select the main loop would chew up 100% of the CPU. Interrupt
> have their place but often complex ISRs are used that aren't any faster
> than polling.

Select probaby uses an ISR

-- 
Renewable energy: Expensive solutions that don't work to a problem that 
doesn't exist instituted by self legalising protection rackets that 
don't protect,  masquerading as public servants who don't serve the public.

Thread

Re: Manipulating C code at the AST level, in C Nuno Silva <nunojsilva@invalid.invalid> - 2026-08-14 12:26 +0100
  Re: Manipulating C code at the AST level, in C Geoff Clare <geoff@clare.See-My-Signature.invalid> - 2026-08-14 13:53 +0100
    Re: Manipulating C code at the AST level, in C Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-08-14 21:10 +0000
  Re: Manipulating C code at the AST level, in C scott@slp53.sl.home (Scott Lurndal) - 2026-08-14 16:00 +0000
  Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-14 23:47 -0400
    Re: Manipulating C code at the AST level, in C rbowman <bowman@montana.com> - 2026-08-15 07:20 +0000
      Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-15 11:33 +0100
      Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-15 22:41 -0400
        Re: Manipulating C code at the AST level, in C "Carlos E. R." <robin_listas@es.invalid> - 2026-08-16 10:50 +0200
    Re: Manipulating C code at the AST level, in C Jim Jackson <jj@franjam.org.uk> - 2026-08-15 11:07 +0000
      Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-15 12:18 +0100
    Re: Manipulating C code at the AST level, in C Richard Kettlewell <invalid@invalid.invalid> - 2026-08-15 12:20 +0100
      Re: Manipulating C code at the AST level, in C c186282 <c186282@nnada.net> - 2026-08-16 02:09 -0400
        Re: Manipulating C code at the AST level, in C Richard Kettlewell <invalid@invalid.invalid> - 2026-08-16 09:59 +0100
          Re: Manipulating C code at the AST level, in C The Natural Philosopher <tnp@invalid.invalid> - 2026-08-16 11:42 +0100

csiph-web