On Mon, 3 Dec 2001, Dan Sugalski wrote: > I'm getting tempted to have some sort of multi-level ENV thing that, for > most single-interpreter cases, collapses down to a plain getenv/putenv.
On a related topic, I have a friend/coworker who's an avid developer of PHP, and we routinely get into, shall we say, comparisons between Perl and PHP. He was telling me about the way PHP seperates the interpreter from the OS-specific stuff via a SAPI layer. It seems to me that Parrot could really use something to this effect. for instance, if I embed Parrot in my billing system, I don't really care about the environment and I don't want/need %ENV. Things that don't deal with the interpretation of the bytecode should be seperated with some abstraction. Any thoughts on this? - D <[EMAIL PROTECTED]>
