From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] lisp
Date: Mon, 7 Jul 2008 13:21:33 -0700 [thread overview]
Message-ID: <3e1162e60807071321m66f3279bwd3eedb1cdcc90d12@mail.gmail.com> (raw)
In-Reply-To: <20080707201552.89F305B4D@mail.bitblocks.com>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
On Mon, Jul 7, 2008 at 1:15 PM, Bakul Shah
<bakul+plan9@bitblocks.com<bakul%2Bplan9@bitblocks.com>>
wrote:
> On Mon, 07 Jul 2008 20:55:36 BST Charles Forsyth <forsyth@terzarima.net>
> wrote:
> > > It contains executable code but it is not an executable in
> > > the sense you don't directly feed it to exec(2). A lisp
> >
> > in the script you gave earlier
> > #!/usr/local/bin/cmucl -script
> > (format t "Hello, World!~%")
> > cmucl is directly executable but that's presumably the original
> > lisp image; where is the new "core image" mentioned that makes
> > the script run quickly?
>
> cmucl is directly executable but it has only enough
> intelligence to load a big lisp.core, which contains all the
> smarts.
>
> Right, then
(format t "Hello, World!~%")
basically gets "read" then compiled then executed right? (thinking REPL
here)
Right? At least that's how SBCL works based on my understanding.
[-- Attachment #2: Type: text/html, Size: 1404 bytes --]
next prev parent reply other threads:[~2008-07-07 20:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 18:15 Bakul Shah
2008-07-07 18:45 ` erik quanstrom
2008-07-07 19:20 ` David Leimbach
2008-07-07 19:44 ` Bakul Shah
2008-07-07 19:55 ` Charles Forsyth
2008-07-07 20:15 ` Bakul Shah
2008-07-07 20:21 ` David Leimbach [this message]
2008-07-07 20:47 ` Bakul Shah
2008-07-07 20:51 ` David Leimbach
2008-07-08 14:08 ` Dave Eckhardt
2008-07-08 15:07 ` David Leimbach
2008-07-08 19:05 ` Bakul Shah
2008-07-08 21:12 ` C H Forsyth
2008-07-08 21:42 ` Bakul Shah
2008-07-07 20:43 ` geoff
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=3e1162e60807071321m66f3279bwd3eedb1cdcc90d12@mail.gmail.com \
--to=leimy2k@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).