opensubscriber
   Find in this group all groups
 
Unknown more information…

e : emacs-devel@gnu.org 4 July 2012 • 7:02AM -0400

Re: Inefficiency in Bgotoifnil byte-code instruction
by Stefan Monnier

REPLY TO AUTHOR
 
REPLY TO GROUP




> 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,


        Stefan


Bookmark with:

Delicious   Digg   reddit   Facebook   StumbleUpon

Related Messages

opensubscriber is not affiliated with the authors of this message nor responsible for its content.