unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: 2QdxY4RzWzUUiLuE@potatochowder.com
To: help-gnu-emacs@gnu.org
Subject: Re: common lisp vs elisp.
Date: Sat, 19 Jun 2021 20:42:39 -0700	[thread overview]
Message-ID: <YM65L34k2LWnEXEu@scrozzle> (raw)
In-Reply-To: <CAGP6POKkm3tDzaFmwEZU2Q1V184Fr1-_228EMuPBZ4SkKPRn7g@mail.gmail.com>

On 2021-06-20 at 11:26:43 +0800,
Hongyi Zhao <hongyi.zhao@gmail.com> wrote:

> On Sun, Jun 20, 2021 at 11:13 AM Emanuel Berg via Users list for the
> GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:

[...]

> > Common Lisp (or CL, 1984) is the industrial-strength Lisp
> > while Emacs Lisp (or Elisp, 1985) is the Emacs
> > domain-specific Lisp.
> 
> So, the following questions come to my mind:
> 
> 1. Does this mean that the former is a superset of the latter?

No.

> 2. What's the standard compiler/debugger for the latter on *nix platforms?

There's not really a standard.  That's one of the great things about
*nix (as opposed to POSIX).  :-)

If you want a free solution, the de facto environment is SBCL
(https://sbcl.org) and SLIME under Emacs.

For a commercial solution, try Allegro
(https://franz.com/products/allegrocl/).

Both implement CLtL2 and have an ANSI standards compliant mode.



  reply	other threads:[~2021-06-20  3:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-20  2:22 common lisp vs elisp Hongyi Zhao
2021-06-20  3:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20  3:26   ` Hongyi Zhao
2021-06-20  3:42     ` 2QdxY4RzWzUUiLuE [this message]
2021-06-20  4:04       ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-06-20  4:44         ` Hongyi Zhao
2021-06-20  6:21           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20  6:36           ` Joost Kremers
2021-06-20  6:57             ` Hongyi Zhao
2021-06-20  7:35               ` Jean Louis
2021-06-20 12:44               ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-27 15:08                 ` Andreas Eder
2021-06-27 15:36                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-28  6:46                     ` Jean Louis
2021-07-06  1:53                       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-06 12:28                         ` Alexandre Garreau
2021-07-06 16:08                           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-20  7:16             ` Jean Louis
2021-06-20  7:04           ` Jean Louis

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=YM65L34k2LWnEXEu@scrozzle \
    --to=2qdxy4rzwzuuilue@potatochowder.com \
    --cc=help-gnu-emacs@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.
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).