Re: Parrot multithreading?

[Dan Sugalski]

At 02:04 PM 9/20/2001 -0700, Damien Neil wrote:
>On Thu, Sep 20, 2001 at 04:57:44PM -0400, Dan Sugalski wrote:
> > >For clarification: do you mean async I/O, or non-blocking I/O?
> >
> > Async. When the interpreter issues a read, for example, it won't assume 
> the
> > read completes immediately.
>
>That sounds like what I would call non-blocking I/O.  Async I/O
>would involve syscalls like aio_read().

Might sound that way, but it isn't. What I'm talking about is something like:

    READ S3, P1, I0
X: SLEEP 3
    EQ I0, 0, X
    PRINT S3

Where we issue the read on the filehandle in P1, telling it to store the 
results in S3, and put the completion status in I0. The sleep will 
presumably be replaced by code that actually does something, and we wait as 
long as the completion register says we're not done.

                                        Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski                          even samurai
[EMAIL PROTECTED]                         have teddy bears and even
                                      teddy bears get drunk