Simon Cozens wrote:
> How much can we do in the compiler, and how much can we do in the
> interpreter? If we're having cached bytecode, it makes sense to do
> as much optimization as we can in the compiler.
I thought, by PDD 1
(http:[EMAIL PROTECTED]/msg02116.html), it
was:
SOURCE CODE
|
| parse
|
V
SYNTAX TREE
|
| compile
|
V
BYTE CODE
|
| optimize
|
V
BYTE CODE
|
| interprete
|
V
(run)
Probably Perl 6 programs will be cached/distributed in optimized byte code
format.
Putting the burden of optimize code above the interpreter allows a quicker
interpreter (since it doesn't need to do expensive optimizations) and allows
more optimized code, since the code can go through a real expensive
optimizator once and be stored to be used by the interpreter many times
(this could be done for distributing the production version of the program).
- Branden
