At 03:11 PM 1/8/01 +0000, Nick Ing-Simmons wrote:
>Dan Sugalski <[EMAIL PROTECTED]> writes:
> >At 01:02 PM 1/6/01 -0500, Uri Guttman wrote:
> >>that is what i would expect form a simple flag test and every N tests
> >>doing a full event poll. and even up to 5-10% slowdown i would think is
> >>a good tradeoff for the flexibilty and ease of design win we get in the
> >>i/o and event guts. but then, i have always traded off speed for
> >>flexibility and ease. hey, so has perl! :)
> >
> >Not always. :) The flexibility really does need to balance out the speed
> >hit. (If Nick wasn't in the middle of rewriting the whole IO system, I'd
> >probably be assaulting sv_gets to make up for the speed hit I introduced
> >way back with the record reading code...)
>
>Nick has yet to touch sv_gets() - partly 'cos it was too scary to mess
>with - so you can if you like ;-)
(As I dig through old mail...)
What I was thinking of was making the scalar behind $/ magic, throwing a
pointer to the current sv_gets function into the interpreter structure, and
then splitting off sv_gets into several little functions. (Or possibly
several big functions, I'm not sure) It'd toss out a few compares from the
head of sv_gets, which'd speed it up a little.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
