>>>>> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
DS> A subsystem is, in this instance at least, a piece of perl that
DS> can more or less stand alone, but cross modules. The regex engine,
DS> for example, is pretty much a black box--hings go in and come out,
DS> an Magic Happens inside. The PerlIO system is similar, as the
DS> parser's likely to use at leas the lowest-level version (all the
DS> functionality that doesn't have perl subs involved) for all its
DS> I/O.
DS> Safe signals live pretty much entirely inside the interpreter
DS> piece, so don't really count as a separate subsystem. They're more
DS> a design goal than anything else.
unfortunately as i have pointed out in the rfc on safe signals, you
can't deliver them without either using an event loop (which is a part
of the i/o subsystem and the interpreter) or code generate inline event
check calls (which is part of the parser or byte code generator). the
third option is to code the event checks manually in the main program
and that doesn't affect any subsystems. so you can't isolate safe
signals easily.
anyhow, that is my $.02. i do see this modular approach being a big win
but there are some things in perl which don't fall into one module. we
have to allow for that in special cases.
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
