RFC - documenting LAP

RFC - documenting LAP

[Rocky Bernstein]

[-- Attachment #1: Type: text/plain, Size: 513 bytes --]

The LAP instruction set isn't documented. I will undertake to make a pass
at it.

At this early stage though, changes to the organization are the easiest to
make; so if you have thoughts, please speak up.

So we have something concrete to discuss, The first stab at this is at
https://github.com/rocky/elisp-lap

I can put this on savanna.gnu.org such as under emacs or somewhere else
pending discussion. However at this stage where it is mostly amorphous and
not filled in, I don't think it really matters much.

[-- Attachment #2: Type: text/html, Size: 715 bytes --]

Re: RFC - documenting LAP

[Rocky Bernstein]

[-- Attachment #1: Type: text/plain, Size: 927 bytes --]

One of the things the LAP/Elisp Bytecode doc should have are notes as to
when certain opcodes were added or removed. Again, I'll cull Changelogs or
git history, but if folks who have made changes want to explain what
changed when and why, that's certainly more friendly than doing the
investigative digging.

Thanks.

On Mon, Dec 18, 2017 at 9:47 PM, Rocky Bernstein <rocky@gnu.org> wrote:

> The LAP instruction set isn't documented. I will undertake to make a pass
> at it.
>
> At this early stage though, changes to the organization are the easiest to
> make; so if you have thoughts, please speak up.
>
> So we have something concrete to discuss, The first stab at this is at
> https://github.com/rocky/elisp-lap
>
> I can put this on savanna.gnu.org such as under emacs or somewhere else
> pending discussion. However at this stage where it is mostly amorphous and
> not filled in, I don't think it really matters much.
>

[-- Attachment #2: Type: text/html, Size: 1461 bytes --]