Closed ghost closed 7 years ago
I thought it was the compiler-interpreter-compiler, in that it compiles PyHP++# into the half compiled, half interpreted state.
That seems... odd. It also wouldn't work outside of a JIT environment, and I don't think anyone here wants to write an entire JIT compiler.
What if by compiled we meant compiled to byte code, or perhaps, transpiled. While not technically compiled, this option would be easier.
There also appears to be libraries for JITing, of course.
Ehhhh, I don't know if we want to go to the effort of building a transpiler/bytecode compiler for PHP just so we can build a compiler/interpreter for a different language.
Maybe it should just be a totally inappropriate name.
It doesn't need to be a bytecode compiler for PHP, we could invent the bytecode language. I also have some experience targeting python byte code, so that could be fun.
If you want to write one, go ahead!
I don't know much PHP, but it looks like there's a PHP compiler here. @alexbuzzbee was right - it is Compiled Interpreter-Compiler.
Can someone explain how a compiled interpreter-compiler would work?
You write a program that interprets and compiles PyHP++# (perhaps to bytecode) and then you compile that program.
If the CIC is supposed to be the compiled interpreter-compiler, how will we compile it if it's written in PHP, an interpreted language?