Brent -- > How about, instead of just saying 'oplib foo' in the bytecode header, we > say 'first N opcodes of oplib foo'? After all, you generally don't have > any use for opcodes added after you assembled. :^)
I agree, although I take it further by allowing you to cherry-pick the ops you need out of the oplib. There should not be any runtime penalty for my approach. Smaller programs have (possibly) smaller opcode tables, and opfunc lookup is as deep as it is now because we flatten the custom opcode table at load time. Regards, -- Gregor
