Newsgroups: comp.lang.lisp
Path: cantaloupe.srv.cs.cmu.edu!bb3.andrew.cmu.edu!newsfeed.pitt.edu!gatech!news.mathworks.com!fu-berlin.de!zrz.TU-Berlin.DE!news.dfn.de!news.dkrz.de!news.rrz.uni-hamburg.de!news.Hanse.DE!wavehh.hanse.de!cracauer
From: cracauer@wavehh.hanse.de (Martin Cracauer)
Subject: Re: CMUCL "save-lisp"
Message-ID: <1996May5.171856.25036@wavehh.hanse.de>
Organization: BSD User Group Hamburg
References: <4m64qv$q0j@bird.cs.ucsb.edu>
Date: Sun, 5 May 96 17:18:56 GMT
Lines: 32

mcguire@cs.ucsb.edu (Hugh W. Mcguire) writes:

>I'm trying to save a lisp-image for fast later restarting of work, but I'm
>encountering difficulties.

>The Lisp that I'm using is CMUCL (which I understand is no longer being
>supported).  The documentation indicates that something like the following
>should work:

>    [from within Lisp:]

>    * (extensions:save-lisp "lcore")

>    * (quit)

>    [now back in the shell]

>    % lisp -core=lcore
                 ^
                 ^

Try `lisp -core lcore` (without '='). CMU CL doesn't give an error
message when an invalid command line argument is given. Your invalid
argument is being ignored and the normal Lisp image loaded. In Unix
you can check for such effects with `ls -lu` on the cores file and you
can see which file actually has been read by the Lisp process.

Martin
-- 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
Martin Cracauer <cracauer@wavehh.hanse.de>  -  BSD User Group Hamburg
BSD, Lisp and other programming info http://www.bik-gmbh.de/~cracauer
