At 7:10 PM -0700 1/17/03, Cory Spencer wrote:
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.
IM
At 10:39 AM 1/18/2003 -0500, [EMAIL PROTECTED] wrote:
The Jako compiler uses imcc as well...
While we are plugging...
and Cola too :)
-Melvin
quot;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/parse
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 no
If memory serves me right, Cory Spencer wrote:
> most example languages implement a complete compiler (ie lexxer -> parser
> -> optimizer -> code emitter), which seems to be somewhat of a
> duplication of labour.
Some are in C, others in pasm and yet others in Perl ... how do do you re-use
libr
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 Mess
