Re: Parrot compilers

[Will Coleda]

I'm working on converting the tcl compiler (written in perl) which targetted imcc into an interpreter written in imcc.

Regards.

[EMAIL PROTECTED] wrote:

The Jako compiler uses imcc as well...

"Tanton Gibbs" <[EMAIL PROTECTED]>
01/18/2003 01:10 AM

To: "Cory Spencer" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
cc: Subject: Re: Parrot compilers


Yes, languages should now use IMCC as their target. Basically, they
generate IMCC instructions without regards for optimization and such so that
only a lexer/parser is needed. Take a look at the bf and ook languages for
an example. I think perl6 is also heading there.

Tanton
----- Original Message -----
From: "Cory Spencer" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, January 17, 2003 9:10 PM
Subject: Parrot compilers

Hey folks -

In my wanders through the parrot/languages subdirectories, it appears

that

most example languages implement a complete compiler (ie lexxer ->

parser

-> optimizer -> code emitter), which seems to be somewhat of a
duplication of labour.  Has or is anyone worked on a framework a la gcc
which would only require that new languages have a lexxer/parser written
that coerced data into a standardized AST which could be passed off to

other

compilation stages? (Similarly, other end targets (such as Java

bytecode

or native code would only require the implementation of a new code
emission module.)

-c

--
Will "Coke" Coleda