Jens Rieks <[EMAIL PROTECTED]> wrote: > Hi all! > I propose the following because the current IMCC reimplementation seems to > make no progress.
I've a different roadmap: 1) specify AST interface 2) implement code generation from AST 3) split PASM and PIR lexer/parser into 2 indpendent compilers 4) have a separate macro pre-processor run e.g. from an IO layer 5) change both PASM/PIR compiler to use the AST interface > ## first part ## > Create a (bytecode) class "PIR" that can be used (by compilers written in > bytecode) as an standardized interface to IMCC. You can already run arbitrary compilers with the C<compreg> interface, when your compiler spits out sourcecode. And it's rather simple to have a compiler written in C (s. examples/compilers/japhc.c). Missing is just some general API but that will be done along with 1). > ## second part ## > Write a PIR lexer/parser in a language targeting parrot W/o some kind of regex support that's a PITA. > jens leo
