unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Rocky Bernstein <rocky@gnu.org>
To: emacs-devel@gnu.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Using the correct terms LAP vs ELisp Bytecode or something else
Date: Thu, 21 Dec 2017 11:56:31 -0500	[thread overview]
Message-ID: <CANCp2gaQA11rxucP3R_U57joEUMkie0heLh=tAAyF3WgEFp3yQ@mail.gmail.com> (raw)

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

Thanks for the information...

On Wed, 20 Dec 2017 20:50:28 -0500 Stefan Monnier <monnier@iro.umontreal.ca>
wrote:

>
> > 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.
>

This is the first I am hearing about LAP code being something that is
accessible from Lisp. Where are packages that work with LAP?

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

             reply	other threads:[~2017-12-21 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 16:56 Rocky Bernstein [this message]
2017-12-21 18:56 ` [SUSPECTED SPAM] Re: 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  0:44 Rocky Bernstein
2017-12-21  1:50 ` Stefan Monnier

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='CANCp2gaQA11rxucP3R_U57joEUMkie0heLh=tAAyF3WgEFp3yQ@mail.gmail.com' \
    --to=rocky@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).