Re: User-reserved element in byte code vectors

[Lars Brinkhoff]

Stefan Monnier <address@hidden> writes:
> >> > No, that's not necessary.  As long as the first six element in the
> >> > byte code object are as Emacs expects them to be, anything can be
> >> > stuffed into additional elements.  At least in GNU Emacs 20.7,
> >> > 21.3, and CVS.
> >> But then how does your bytecode access this 7th element?
> > Yes, that's a problem.  I don't think there is a way.
> Heh?  Do you mean to say that "your way" has the downside that it
> plain does not work?

Yes, that's a slight disadvantage. :)  This would only be under
consideration for "question two" below.  But then, Miles's funcallable
vectors may be better.

> I thought you already had it implemented.

I'm using another way which I sketched in a message a few days ago.

> Well, there are two questions:
> - how best to implement closures, given the current Emacs C code.
> - how best to implement closures, assuming we get to change the C code.
> 
> I'm talking about the first question.  Miles's work is within the context
> of the second.

I'm interested in both.

-- 
Lars Brinkhoff,         Services for Unix, Linux, GCC, HTTP
Brinkhoff Consulting    http://www.brinkhoff.se/