In article <BDC.96Mar28110211@berne.ai.mit.edu>,
Brian D. Carlstrom <email@example.com> wrote:
>>>> Scott Draves writes:
>In article <SPOT.96Mar20151805@sandoz.slip.cs.cmu.edu>
>firstname.lastname@example.org (Scott Draves) writes:
> > has someone written a pickler for scsh? that is, a routine that
> > can store part of the heap (including primops and loops) to a
> > file, then later restore it?
>Scheme 48 had a pickler of some sort at one time, but I don't see it
>anywhere obvious in the version we are using. It wasn't complete, but it
>could be used for data. Olin, do you remember where it was. You showed
>it to me.
You mean like
,dump <filename> [<identification>]
This writes out the current heap. When the new image is resumed,
it starts in the command processor. If present, <identification>
should be a string (written with double quotes); this string will
be part of the greeting message as the image starts up.
,build <exp> <filename>
<exp> should evaluate to a procedure of one argument. When
<filename> is resumed, that procedure will be invoked on the VM's
-a arguments, which are passed as a list of strings. The
procedure should return an integer (as for ,exit). The command
processor and debugging system are not included in the image
(unless you go to some effort to preserve them, such as retaining
Doing ",flush" before building an image will make for smaller
images, but if an error occurs, the error message may be less
helpful. Doing ",flush source maps" before loading any programs
will make the image still smaller.