On Mon, Jan 08, 2001 at 11:39:11AM +0100, Bart Lateur wrote: > >This is the Perl interpreter: > > while ((PL_op = CALL_FPTR(PL_op->op_ppaddr)(aTHX))) { > > PERL_ASYNC_CHECK(); > > } > > > >The only problem is that right now, PERL_ASYNC_CHECK doesn't actually > >do anything. :) > > I don't get it. Does this *have* to give a 3-5% performance hit? Even if > you do it this way (syntax is a Perlish extension to C): > > while ((PL_op = CALL_FPTR(PL_op->op_ppaddr)(aTHX))) { > async_waiting or next; > PERL_ASYNC_PROCESS(); > } Which is what PERL_ASYNC_CHECK was scheduled (if you've pardon the pun) to do. -- "Darkly hinting of head hitting desk" -- Megahal (trained on asr), 1998-11-05
- Re: perl IS an event loop (... Jarkko Hietaniemi
- Re: perl IS an event loop (... Uri Guttman
- Re: perl IS an event loop (... Dan Sugalski
- safe signals (was Re: perl ... Nicholas Clark
- Re: perl IS an event loop (... Uri Guttman
- Re: perl IS an event loop (... Uri Guttman
- Re: perl IS an event loop (... Dan Sugalski
- Re: perl IS an event loop (... Nick Ing-Simmons
- Re: perl IS an event loop (... Nick Ing-Simmons
- Re: perl IS an event loop (was ... Bart Lateur
- Re: perl IS an event loop (... Simon Cozens
- Re: perl IS an event loop (... Nick Ing-Simmons
- Re: perl IS an event loop (... Uri Guttman
- Re: Speaking of signals... nick
- Re: Speaking of signals... Filipe Brandenburger
- Re: Speaking of signals... Damien Neil
- Re: Speaking of signals... Nicholas Clark