From: Austin Ziegler <austin@...>
Date: 2002-11-12T04:12:05+09:00
Subject: Re: A vision for Parrot

On Tue, 12 Nov 2002 03:46:30 +0900, Darren New wrote:
> Benjamin Goldberg wrote:
>> In all cases that I can think of, your dynamic code is
>> essentially a string which gets eval()ed (with a
>> language-dependent eval). The solution is to make the eval()
>> function/operator compile into a sequence of operations along the
>> lines of: Load the compiler for this language, (if it's not
>> already loaded), pass that string to the compiler, run the
>> generated bytecode.
> Seems like an awful lot of overhead for every keystroke, window
> event, and async file operation.

Mmmm, no. The bytecode engine will have the "os-level" services for
those things. What Benjamin was talking about is when you get "raw"
Ruby, Perl, Tcl, or Python at the VM level instead of the bytecodes
being expected. "Raw" code should be a rare event, even with
scripting languages. If it's not going to be a rare event, then IMO
you need to reconsider how your application is being written.

-austin
-- Austin Ziegler, austin@halostatue.ca on 2002.11.11 at 14.07.21