Re: [Emacs-diffs] /srv/bzr/emacs/trunk r109327: Generalize INTERNAL_FIELD between buffers, keyboards and frames.

[Stefan Monnier <monnier@IRO.UMontreal.CA>]

>>> * src/frame.h (FVAR): New macro.
>> Is it really necessary?  To me this just obfuscates the code.
>> If/when it turns out to be needed, it'll be easy enough to introduce.
> I have no ideas why BVAR and KVAR was introduced, but my motivation is:

Then, please undo your changes.  The INTERNAL_FIELD part is fine, but
the new FVAR, WVAR, ... are not.  Maybe it can be useful as an
intermediate step on some separate generational-gc branch, but it
doesn't have its place in trunk: I can't think of any way to make such
macros give realistic performance with anything but a write-barrier, so
such macros will only ever be needed for write accesses and never for
read-accesses.
So you're obfuscating the read-accesses (i.e. the most common case) for
no good reason.
I'm OK with introducing such macros to *set* such fields (i.e. for write
barriers), but not to read them (at least not until there's a really
good case for them).


        Stefan