From: Rocky Bernstein <rocky@gnu.org>
To: emacs-devel@gnu.org
Subject: Using the correct terms LAP vs ELisp Bytecode or something else
Date: Wed, 20 Dec 2017 19:44:31 -0500 [thread overview]
Message-ID: <CANCp2gYPPENGqrvTKu6iD0eDu1uFnnKgPQmtQxGDpY1hQR-twg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
What's the difference between LAP and Elisp Bytecode (if that is the right
term)?
LAP stands for Lisp Assembly Program, so I imagine that refers to the text
representation. Bytecode however generally refers to a more binary
representation, but I guess often it includes the mnemonics for the code.
If I want to describe the the assembly instructions, should I refer to it
as LAP instructions or Elisp bytecode instructions or Emacs Lisp bytecode
instructions?
And is it "bytecode' or "byte code"?
Or maybe there aren't any conventions and none of this matters so I can
just use whatever I feel like.
Please advise. Thanks.
[-- Attachment #2: Type: text/html, Size: 743 bytes --]
next reply other threads:[~2017-12-21 0:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 0:44 Rocky Bernstein [this message]
2017-12-21 1:50 ` Using the correct terms LAP vs ELisp Bytecode or something else Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2017-12-21 16:56 Rocky Bernstein
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANCp2gYPPENGqrvTKu6iD0eDu1uFnnKgPQmtQxGDpY1hQR-twg@mail.gmail.com \
--to=rocky@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).