Re: Help with adding an auxiliary bytecode table

[Stefan Monnier]

> I've attached a diff below that adds an auxiliary optable to bytecode.c
> and attempts to integrate it into bytecode.el. I can run emacs -Q with
> it, but when I run it with my configuration I get the following in
> stderr:
>
>   Invalid function: ((bytecomp "Wrong type argument: arrayp, nil" :error
>   "*Compile-Log*"))

Use the debugger so you can get a more complete backtrace.

> My initial reaction is that the stale bytecode is somehow incompatible,

What/which stale bytecode?

> The problem is that since memq is a bytecode operation, it turns out
> to be faster than vector-memq for small input

Why is that a problem?

> unless I make sure that memq isn't turned into a bytecode op.
> So since the current space in the lookup table is limited, I figured
> that a prefix command that looks up in a secondary table would be
> a good solution.

We don't have too many bytecodes left, indeed, but there are still some,
IIRC, so it's not indispensable to go a 2-byte bytecodes.


        Stefan