Dan Sugalski <[EMAIL PROTECTED]> wrote: > Right now there's a load_pmc op, which goes along with the load_opcode_lib > and loadlib ops. I'd like to unify that
I'll start the opcode load thingy, based on my experimental code I has posted here mid-March. The basics are: - assembler and runtime must see the C<loadlib> "oplib" in the same sequence, because - the opcode numbers are assigned dynamically: When you load an oplib containing 100 ops, they get op numbers e.g. 1206 ... 1305. Next oplib starts at 1306 ... - on load all runcores are notified to use the new oplib function or address table There are for sure issues e.g. when you run the CGP core and the loaded lib has functions only, but a default handler in the jump table can call these functions then. The switched core also need this default handling. > ... Parrot_lib_load_%s ... > ... returns a PMC representing the library Any hints, what kind of PMC that shall be? An new Parrot_Lib PMC with the dll handle attached + some flags about the library and its contents? > Dan leo
