[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Inefficiency in Bgotoifnil byte-code instruction

From: Stefan Monnier
Subject: Re: Inefficiency in Bgotoifnil byte-code instruction
Date: Tue, 03 Jul 2012 19:02:38 -0400
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1.50 (gnu/linux)

> I took the "value" approach because the bytecode values are fixed, and I
> thought it was safer to be explicit about them.
> The backslashes are just needed because I made one big #define.

Yes, as I said, I think it's OK.  Maybe better would be if the threaded
version actually checked that the `value' is correct (i.e. is one more
than the previous one) rather than just ignore that argument.

> Another approach (used in gcc, gdb, etc) is to put the opcode defines
> into a ".def" file and then include it in multiple places.

I'm not sure it's better, since, as you say, the values are fixed by
external factors.

Feel free to install,


reply via email to

[Prev in Thread] Current Thread [Next in Thread]