Re: Speaking of signals...

[Uri Guttman]

>>>>> "RC" == Rocco Caputo <[EMAIL PROTECTED]> writes:

  RC> With a tightly integrated event loop, blocking perl level I/O can be
  RC> implemented in terms of internal asynchronous I/O.  An interpreter can
  RC> then block while perl is free to do other things, like say run other
  RC> interpreters.

doing this at the perl language level is easy since we control the stack
and program counter. try doing it at the c level in the guts without
munging the stack in ugly ways. by having the guts of perl always assume
it is running in an event loop, we can get all these features without
any ugly code.

uri

-- 
Uri Guttman  ---------  [EMAIL PROTECTED]  ----------  http://www.sysarch.com
SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX Consulting
The Perl Books Page  -----------  http://www.sysarch.com/cgi-bin/perl_books
The Best Search Engine on the Net  ----------  http://www.northernlight.com