On Tue, 08 Jul 2008 08:07:59 PDT "David Leimbach" <[EMAIL PROTECTED]> wrote: > > On Tue, Jul 8, 2008 at 7:08 AM, Dave Eckhardt > <[EMAIL PROTECTED]<[EMAIL PROTECTED]>> > 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 had asked my friend who ported CMUCL to Windows about this. He too first looked at SBCL but found it hard to port and the bootstrapping process was a lot longer. He was then able to create the initial CMUCL port by porting just the runtime -- he added just enough of a compatibility layer to allow use of a FreeBSD core image. Compiled Lisp object would think it is running on FreeBSD. > I like Dave Eckhardt's idea. I don't think core files get changed that > often, In the olden days Lisps used to create a custom executable by storing the heap in a data segment. Something to look into.
