From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] lisp
Date: Tue, 8 Jul 2008 08:07:59 -0700 [thread overview]
Message-ID: <3e1162e60807080807n72028e01vbe117c358fecd65@mail.gmail.com> (raw)
In-Reply-To: <23384.1215526099@lunacy.ugrad.cs.cmu.edu>
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
On Tue, Jul 8, 2008 at 7:08 AM, Dave Eckhardt
<davide+p9@cs.cmu.edu<davide%2Bp9@cs.cmu.edu>>
wrote:
> > cmucl is directly executable but it has only enough
> > intelligence to load a big lisp.core, which contains
> > all the smarts.
>
> If these core files aren't generated all *that* often,
> one could write a tool which would turn a core file
> into a byte array, link a new lisp executable, and
> exec() that. I realize that's not an answer to the
> question as posed, but...
>
> Dave Eckhardt
>
> I'm not sure if any action is being taken just yet on which Lisp to "go
for" but, if I were porting a lisp I'd be looking at either CMUCL or SBCL,
and probably lean more towards SBCL, as they've done a bit of work to make
bootstrapping a little nicer.
I like Dave Eckhardt's idea. I don't think core files get changed that
often, however sometimes when one produces a "standalone" product from one
of the above SBCL or CMUCL, you do want to make your own core file and
distribute it. That's still a pretty static process if my memory serves me.
Dave
[-- Attachment #2: Type: text/html, Size: 1428 bytes --]
next prev parent reply other threads:[~2008-07-08 15:07 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
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 [this message]
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=3e1162e60807080807n72028e01vbe117c358fecd65@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).