#624: pluggable everything
---------------------+------------------------------------------------------
Reporter: allison | Owner: allison
Type: roadmap | Status: new
Priority: normal | Milestone: 3.6
Component: none | Version:
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
---------------------+------------------------------------------------------
Comment(by whiteknight):
If a user was so industrious as to write his own compiler for PIR or PASM,
they should definitely be able to use that instead, yes. We need to think
bigger though. What if a person wanted to write the compiler for an HLL in
Lex/Yacc/C instead of in PCT? What if the Lua team wanted to write the Lua
parser in C for performance reasons? They would swap out IMCC with a
pluggable Lua compiler frontend and use that to compile directly to
bytecode.
Also think about runtime calls to compreg, which could load either a .pbc
library file that contained a PCT-based compiler, or could load a shared
binary library that implements the frontend for it instead. This is how
the PIR compreg could work, and could be loadable dynamically if needed
(and not loaded at all if not needed).
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/624#comment:7>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
