At 05:23 PM 9/20/2001 -0400, Michael L Maraist wrote: >There wasn't any code for CHECK_EVENTS w/in Parrot when I first read the >source-code. I merely assumed that it's role was not-yet determined, but >considered the possible uses. CHECK_EVENTS seems to be gone at the >moment, so it's a moot point. There probably won't be any. The current thinking is that since the ops themselves will be a lot smaller, we'll have an explicit event checking op that the compiler will liberally scatter through the generated code. Less overhead that way. Dan --------------------------------------"it's like this"------------------- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
- Re: Parrot multithreading? Michael L Maraist
- Re: Parrot multithreading? Rocco Caputo
- Re: Parrot multithreading? Dan Sugalski
- RE: Parrot multithreading? Dan Sugalski
- Re: Parrot multithreading? Damien Neil
- Re: Parrot multithreading? Dan Sugalski
- RE: Parrot multithreading? Hong Zhang
- Re: Parrot multithreading? Damien Neil
- Re: Parrot multithreading? Uri Guttman
- Re: SV: Parrot multithreading? Michael L Maraist
- Re: Parrot multithreading? Dan Sugalski
- Re: Parrot multithreading? Dan Sugalski
- Re: Parrot multithreading? Uri Guttman
- RE: Parrot multithreading? Hong Zhang
- Re: SV: Parrot multithreading? Uri Guttman
- Re: SV: Parrot multithreading? Dan Sugalski
- Re: SV: Parrot multithreading? Uri Guttman
- Re: SV: Parrot multithreading? Dan Sugalski
- Re: SV: Parrot multithreading? Michael Maraist
- Re: SV: Parrot multithreading? Michael Maraist
- Re: SV: Parrot multithreading? Dan Sugalski