On Sun, 20 Jul 2003, Dan Sugalski wrote:
>It would be entirely possible for Parrot (or a Parrot library) to >use AIO at a low level, without introducing interrupts to the VM layer.
Sure. But what'd be the point? Adding in interrupts allows a number of high-performance idioms that aren't available without them. They certainly won't be required, and most of the IO you'll see done will be entirely synchronous, since that's what most compilers will be spitting out. You don't *have* to use IO callbacks, you just can if you want to.
Hey Dan,
I'm just curious... When you say IO callbacks, does that mean external C code calling back into the parrot VM?
That should work just fine, though it wasn't what I was talking about.
Will that kind of locking be necessary in parrot, or would these IO callbacks allow outside DLL's to callback to parrot code automatically?
There'll have to be some mechanism defined, depending on what you want to do--you'll be able to choose either posting an event to the queue for processing, or calling directly back in. There'll be limitations with both, but they shouldn't be bad.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
