Re: User-reserved element in byte code vectors

[Lars Brinkhoff]

Richard Stallman <address@hidden> writes:
>     > I recommend leaving the first slot after `curry' unused.  That
>     > way it could be used later to control extensions, such as a
>     > feature to specify the order of curried and noncurried
>     > arguments.
>     I don't think that's really necessary.
> My idea is that it would say where to fit the new args around the
> old args.  For instance, you might want to curry args 2 and 3.  This
> would be easy if the first slot has a list saying where the curried
> args go.  For instance, a list of integers saying which positions to
> use the curried args in.

For what it's worth, I agree with Stefan Monnier.  There's really no
need to over-engineer this.  Emacs Lisp can already do all kinds of
fancy currying without the proposed change.

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