petdance/scratch — Issue #423: Parrot_compile_file should take a compiler argument
Author: petdance
Created: 2011-11-01 04:25:59+00:00
State: open

Parrot_compile_file assumes libparrot has a PASM or PIR compreg registered, and uses one of those to compile. Don't do this. Parrot_compile_file should take a PMC* argument for a compiler object to use, and the user should be able to either specify a default compiler to use, or should be able to set up a mapping between file-extension/mime-type -> compiler at the global/interpreter level.

Better yet, create a new function with a better name and the new signature, deprecate Parrot_compile_file, and migrate over time.