3 ms·
> But I don't want to restart in whatever garbled development state I'm currently in. Right; the thing to is to start a completely new image, and the only thin
by kazinator 6y ago
> But I don't want to restart in whatever garbled development state I'm currently in.
Right; the thing to is to start a completely new image, and the only thing you do in this image is load all of your compiled files, and then call the image-saving function.
This was pretty obvious to me, coming from a C background.
My first Lisp programs used Makefiles to do this stuff.
You don't want to sit there and making deployed executables manually out of your dirty hacking session, of course.
> I want execution to begin at the entry point
Common Lisp implementations typically offer some image saving function, which has an argument for specifying something to be evaluated when that image is restarted, or a function to be called or some such.
This general area is called "application delivery": you have to investigate the ways that your Lisp implementation offers application delivery. Saving an image might not be the only way; there may be a way to create an executable which isn't a saved image. In some Lisps, the hash-bang mechanism is supported, and that is appropriate in some situations. Some Lisps can produce shared library, even.