From: Christopher B. <cbb...@gm...> - 2008-08-20 14:18:33
|
On Wed, Aug 20, 2008 at 1:14 PM, Raymond Toy (RT/EUS) <ray...@er...> wrote: > Stephen Compall wrote: >> gusti <ggh...@gm...> writes: >>> What is correct way to write the next "sbcl" command in "clisp" ? The >>> main problem is that we have not "save-lisp-and-die" command in clisp. >> >> http://clisp.cons.org/impnotes/image.html >> >> If you require a memory corruption feature ("and-die"), you will have >> to implement it yourself as a CLISP extension. > > Why is "and-die" a memory corruption feature? > > Was this a joke? No, historically this is how memory dumps have gotten generated for applications that have really complex states where it's nice to pregenerate it. TeX has long been an example of this; search for info on "initex", and generating .fmt files... Emacs historically did the same, I think. -- http://linuxfinances.info/info/linuxdistributions.html "The definition of insanity is doing the same thing over and over and expecting different results." -- assortedly attributed to Albert Einstein, Benjamin Franklin, Rita Mae Brown, and Rudyard Kipling |