unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Pascal Bourguignon <pjb@informatimago.com>
Subject: Re: Problem about source code of lisp
Date: Sun, 17 Sep 2006 03:52:11 +0200	[thread overview]
Message-ID: <87zmcz1cqc.fsf@thalassa.informatimago.com> (raw)
In-Reply-To: eei73b$jme$1@news.yaako.com

"jronald" <followait@163.com> writes:
> I want to learn some principles of the implementation of lisp. I can't find 
> any doc.I have downloaded the clisp source. After untar, its size if 18.6M. 
> There are many .d and .lisp files, and a few .c files. I don't know how to 
> start. Could anyone help me? 

I wouldn't start with a full Common Lisp implementation.

First, read SICP
http://mitpress.mit.edu/sicp/full-text/book/book-Z-H-4.html
You'll find Chapter 4 interesting.

Then you may want to buy and read "LISP IN SMALL PIECES" (no on-line version)
http://www-spi.lip6.fr/~queinnec/WWW/LiSP.html

or read a CL implementation sources, but I'd advise one that is
written in Lisp, not one written in C like "C"lisp.

Have a look at the sources of OpenMCL, probably the cleanest, or of
SBCL.  They have only little bootstrap C or assembly code, compared to
emacs lisp or clisp that are mostly written in C.

On the other hand, one part that might be interesting to read in clisp
is the compiler, which is written in lisp and is simplier than the
other compilers since it targets a lisp-friendly virtual machine.

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/

"I have challenged the entire quality assurance team to a Bat-Leth
contest.  They will not concern us again."

  parent reply	other threads:[~2006-09-17  1:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-17  0:00 Problem about source code of lisp jronald
2006-09-17  1:26 ` Adam
2006-09-17  1:52 ` Pascal Bourguignon [this message]
2006-09-19 17:29 ` robert.thorpe

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=87zmcz1cqc.fsf@thalassa.informatimago.com \
    --to=pjb@informatimago.com \
    /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).