The dynop_mapping branch is an attempt to deal with the dynop numbering issue when loading PBCs that use different dynoplibs in possibly different orders. It is currently in working condition, albeit with a few snags: * There is no longer a global table of opcodes, so OpLib needs rethinking. Maybe the user should specify which opcode library is being referenced. * Packfile bytecode segments now have structure which I've been unable to emulate using PackfileRawSegment. Maybe this needs a new PackfileBytecodeSegment. * There are a number of places that are probably suboptimal, especially in the generation of PBCs.
Should these problems delay the merge of this branch? _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
