On Tue, Sep 26, 2000 at 02:04:58PM -0400, Dan Sugalski wrote: > What'd be a larger win would be if we have async I/O built into the core > I/O subsystem. That way we could queue up requests for blocks of data > (whatever data we want, in this case bytecode) and have them fetched while > we're parsing what's already been loaded. That's a succint version of what I was asking for. :) -- Asynchronous inputs are at the root of our race problems. -- D. Winker and F. Prosser
- RFC 310 (v1) Ordered bytecode Perl6 RFC Librarian
- Re: RFC 310 (v1) Ordered bytecode Michael Maraist
- Re: RFC 310 (v1) Ordered bytecode Simon Cozens
- Re: RFC 310 (v1) Ordered bytecode Dan Sugalski
- Re: RFC 310 (v1) Ordered bytecode Dave Storrs
- Re: RFC 310 (v1) Ordered bytecode Dan Sugalski
- Re: RFC 310 (v1) Ordered bytecod... Uri Guttman
- Re: RFC 310 (v1) Ordered bytecode Simon Cozens
- Re: RFC 310 (v1) Ordered bytecode Dan Sugalski
- Re: RFC 310 (v1) Ordered bytecode Tom Hughes
- Re: RFC 310 (v1) Ordered bytecode Uri Guttman
- Re: RFC 310 (v1) Ordered bytecod... Dan Sugalski
- Re: RFC 310 (v1) Ordered byt... Simon Cozens
- Re: RFC 310 (v1) Ordered... Uri Guttman
- Re: RFC 310 (v1) Ordered... Dan Sugalski
- Re: RFC 310 (v1) Ordered byt... Tom Hughes
- Re: RFC 310 (v1) Ordered... Dan Sugalski
- Re: RFC 310 (v1) Ordered bytecod... Tom Hughes