On Sat, Nov 03, 2001 at 07:17:49PM -0500, Gregor N. Purdy wrote:
> I've been working on this. I've added an opcode_table section that
> contains (oplib, opindex) pairs (they are constant table string indexes to
> allow lookup by name). The custom opcode table for the bytecode in the
> packfile is produced by scanning this, loading oplibs as they are
> referenced. The opcodes for the bytecode are presented in order, and only
> the opcodes actually used need be mentioned. So, opcode N for one bytecode
> chunk could be a totally different opcode from opcode N in a different
> bytecode chunk.
This sounds much better then either of my plans. (OTOH, I'd like to see the
overhead from the larger number of opcode adds.) I'm going to keep working,
and see how our implementations differ.
-=- James Mastros
