From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: Using the correct terms LAP vs ELisp Bytecode or something else
Date: Wed, 20 Dec 2017 20:50:28 -0500 [thread overview]
Message-ID: <jwv37446eny.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: CANCp2gYPPENGqrvTKu6iD0eDu1uFnnKgPQmtQxGDpY1hQR-twg@mail.gmail.com
> 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.
IIRC, LAP code is represented as a list (or is it a vector?) where each
instruction is represented by a symbol with some arguments. So it's not
a textual representation, but it's a "symbolic" representation that's
fairly easy to manipulate and with many similarities to traditional
assembly: use of labels instead of actual addresses, use of
pseudo-instructions (e.g. labels), and things like that.
> Bytecode however generally refers to a more binary
> representation, but I guess often it includes the mnemonics for the code.
Elisp bytecode is represented as a unibyte string (i.e. an array of
bytes), so yes, it's a lot more binary. It's the "garbage" that used to
show up in backtraces.
> 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?
I think you can talk about the "bytecode instruction" and have that
include both the LAP representation of that instruction and its actual
bytecode representation: either the difference doesn't matter, or the
context should make it clear which is meant.
> And is it "bytecode' or "byte code"?
No opinion on that.
> Or maybe there aren't any conventions and none of this matters so I can
> just use whatever I feel like.
Pretty much, yes.
Stefan
next prev parent reply other threads:[~2017-12-21 1:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 0:44 Using the correct terms LAP vs ELisp Bytecode or something else Rocky Bernstein
2017-12-21 1:50 ` Stefan Monnier [this message]
-- 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv37446eny.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.