> I'd have thought it made sense to define it as a bytecode_t type, or
> some such which could be platform specific.

It is better called opcode_t, since we are not using bytecode anyway.

Hong

Reply via email to