Dan Sugalski <[EMAIL PROTECTED]> wrote: > Just to double-check--it's OK to register *any* sub as a compiler > module, though for right now it'll ultimately need to call compile > itself to either the pasm or pir compiler module and return the > result of that, yes?
That's more a matter of definition then anything else. As long as you can invoke the returned thingy, and it does run the code, it doesn't really matter. It just differs when it comes to writing the compiled compiler code to disc as e.g. F<languages/parrot_compiler/parrot.pasm> does. leo
