Klaas-Jan Stol wrote:
Hi,
I've spent some time on refactoring imcc's parser and lexer a bit (only
minor) and I guess the time has come for some design decisions, if possible.
Currently, IMCC handles both PIR and PASM. smash++ suggested that PDDs
should be finished for both PASM and PIR.
Once PASM has been well-defined, a PASM assembler can be written, and the
same for PIR. We'd need to decide how to compile PIR, maybe several options
using commandline options, for isntance PIR->PBC, PIR->PASM, etc. I'm
willing to spend some time on it (as long as I have bits time and don't have
to find a real job), but I can't make these decisions by myself.
If time allows it, it would be nice to have these 2 PDDs around.
Smash and I have been communicating about about the PIR PDD
(docs/pdds/draft/pdd19_pir.pod). He has started it, and is continuing to
refine it. Anyone is welcome to pitch in on that. He'll let me know when
it's ready to review, and I'll give it a final workout before launch. A
group draft followed by architect review/revise is a great way to keep
architectural consistency without blocking on one person's time. It's
especially appropriate with this topic, since we have a good number of
people around who have used PIR, and so have a sense of how it works and
how it could be better.
The PASM PDD (docs/pdds/draft/pdd06_pasm.pod) is open to the same
treatment, if anyone wants to volunteer to take point on the drafting
process.
Allison
