Re: Optional Separate Programs for Interpreter Passes

2000-08-31 Thread Ken Fox
Fisher Mark wrote: > The rest of us with our TVs, VCRs, and so on have only compiled > code in our devices. I'd buy a microwave that resets to 'JAPH' after a power failure. Maybe. ;) - Ken

RE: Optional Separate Programs for Interpreter Passes

2000-08-30 Thread Fisher Mark
Bradley M. Kuhn wrote: > For the world of the JVM port, it's imperative that hooks be > provided so > that the front-end can be run independently, and a different > back-end can be > run (to emit bytecode of some sort). All this also dovetails nicely with the mass-market world of embedded devic

Re: Optional Separate Programs for Interpreter Passes

2000-08-30 Thread Bradley M. Kuhn
Dan Sugalski wrote: > At 12:58 PM 8/29/00 -0500, Fisher Mark wrote: > >Although Perl interpretation is divided into several passes (parser/lexer, > >optimizer, tree/bytecode runner), all these passes are grouped together in > >one binary. Under some memory-constrained conditions, it could be bett

Re: Optional Separate Programs for Interpreter Passes

2000-08-29 Thread Dan Sugalski
At 12:58 PM 8/29/00 -0500, Fisher Mark wrote: >Although Perl interpretation is divided into several passes (parser/lexer, >optimizer, tree/bytecode runner), all these passes are grouped together in >one binary. Under some memory-constrained conditions, it could be better if >each pass ran as its

Optional Separate Programs for Interpreter Passes

2000-08-29 Thread Fisher Mark
Although Perl interpretation is divided into several passes (parser/lexer, optimizer, tree/bytecode runner), all these passes are grouped together in one binary. Under some memory-constrained conditions, it could be better if each pass ran as its own program, passing the transformed data onto the