unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Jean-Christophe Helary
	<jean.christophe.helary@traduction-libre.org>,
	Emacs developers <emacs-devel@gnu.org>
Subject: RE: list of elisp primitives ?
Date: Thu, 26 Dec 2019 10:09:36 -0800 (PST)	[thread overview]
Message-ID: <153c262b-d4f6-4fc4-9fc2-57c58312ae1f@default> (raw)
In-Reply-To: <701C773A-96C5-47FD-B75F-92947976E57B@traduction-libre.org>

> I'm not suggesting that implementing lisp functions
> in C is related to ease of learning or anything.
> 
> My idea, which may be wrong, is that lisp code uses
> building blocks to provide more advanced functions
> and that the most basic blocks are lisp functions
> implemented in C.

Don't confuse building blocks for implementing Lisp
in C with building blocks for defining Lisp in Lisp,
which I suspect is really what you're after: a set
of primitive Lisp constructs that can be used to
define the rest of the language.

> Hence, knowing the building blocks (or a few dozen
> useful ones) can give a clearer idea of what to do
> with elisp in general.

There are various alternative subsets of Lisp
constructs that can be used to do this.  If `cond'
is a primitive then you can implement `if', and vice
versa, for example.

A Lisp definition of `eval' might get you started:

https://igor.io/2013/04/03/sexpr-meta-eval.html

As Marcin pointed out, the search term you want,
when looking for info about this, is "metacircular
interpreter".



  parent reply	other threads:[~2019-12-26 18:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-22  2:59 list of elisp primitives ? Jean-Christophe Helary
2019-12-22  3:21 ` Eduardo Ochs
2019-12-22  3:43   ` Jean-Christophe Helary
     [not found]     ` <CADs++6hB7ZKnEWOZ=XOGdA=W_CacCE2=354ARfNFtWvStaCF3g@mail.gmail.com>
2019-12-22  4:14       ` Jean-Christophe Helary
     [not found]         ` <CADs++6j+niJy3hvrTEJ-LrqcitFuffX=1Duca7pU30a8qfh_zg@mail.gmail.com>
2019-12-22  4:38           ` Jean-Christophe Helary
2019-12-22 15:01         ` Stephen Berman
2019-12-22 17:31         ` Drew Adams
2019-12-26 17:39           ` Jean-Christophe Helary
2019-12-26 18:00             ` arthur miller
2019-12-26 18:09             ` Drew Adams [this message]
2019-12-26 18:22               ` Jean-Christophe Helary
2019-12-26 18:33             ` Stefan Monnier
2019-12-26 21:17             ` Eduardo Ochs
2019-12-27  0:21               ` Jean-Christophe Helary
2019-12-22 14:56     ` Óscar Fuentes
2019-12-22 22:34       ` Jean-Christophe Helary
2019-12-22 19:21 ` Marcin Borkowski

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=153c262b-d4f6-4fc4-9fc2-57c58312ae1f@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=jean.christophe.helary@traduction-libre.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).