On Mon, Jul 15, 2002 at 12:16:29AM -0400, Melvin Smith wrote:
> 1) Async support. The IO system needs to be asynchronous and re-entrant
> at the core, whether by threads or by use of the platform's async support.
> Other things like callbacks assume other features of Parrot to be finished,
> like subs/methods.
Out of curiosity, what's the motivation for supporting true signal-driven
async IO (which is what you seem to be referring to)? In my experience,
nonblocking IO and a standard event loop is more than sufficient, and
far easier to implement--especially portably.
- Damien
