Melvin Smith <[EMAIL PROTECTED]> wrote: > I don't like the idea of IMCC becoming so tightly coupled with the > interpreter. I still wish to be able to build it standalone. Hopefully > we can keep this in mind going forward.
IMCC_INFO is a macro, easily changable. But building it standalone would need some additional defines for PBC building and and the compiler callbacks. Anyway, why would you want to build it w/o parrot? The imcc files are supposed to move down one directory soon. There is no imcc$(EXE) anymore. Your baby evolved - its parrot :) > -Melvin leo
