Joshua Hoblitt wrote:
Is it just me or is it b0rked to have a file named src/parrot.c that does nothing while the entry point for the parrot executable lives in imcc/main.c?
Around 2 years ago test_main.c was Parrot's main and imcc was a standalone PIR->PASM translator. With the integration of imcc, Parrot got embedded into the latter and imcc/main.c became the main entrypoint.
But this is probably just an intermediate step. Parrot integrates currently three "compilers": PASM, PIR, and PAST. But compilers can be registered at runtime too. Therefore Parrot startup will eventually look like this:
- start main in src/parrot.c - determine source file type to compile/run - handle execution over to xxx-compiler or to pbc-run. leo
