Melvin Smith <[EMAIL PROTECTED]> wrote: > I've asked this before: Please, someone give me an example > where a dynamic opcode lib gives us something > that a well designed set of core ops and an extension > interface does not.
Can you explain the difference? Dynamic opcode libraries are extensions to our core opcode set. Its debatable what shall be an opcode or better be a callable function. But opcodes are the primary execution parts of the VM. When speed matters, a piece of code is better a separate opcode then a function bound to some PMC. > -Melvin leo
