[Gcl-devel] Re: persistence in lisp

[Camm Maguire]

The following message is a courtesy copy of an article
that has been posted to comp.lang.lisp as well.

Greetings!

Many systems likely have the equivalent, but in GCL, the exact running
memory image is dumped to disk when evaluating (si::save-system
"new_image").  The resulting file is an ordinary executable which,
when run, will reproduce the state of memory precisely where you left
off.  Thanks to emacs' unexec.

Take care,

Gisle Sælensminde <address@hidden> writes:

> On 2004-11-28, Alex Mizrahi <address@hidden> wrote:
> > Hello, All!
> >
> > i want state of my data to be persistent - system should be able to restore
> > itself after reboot, but without hassle like keeping data in relational db
> > (one of reasons i do it in lisp is because i don't want to use relational
> > db - i just want to use some classes/structs and work with them).
> > it's not hard to do save and load functions for my data, but since lisp
> > supports reflection, it would be nice if it will do serialization code
> > itself.
> > i've looked through CL-PREVALENCE lib. there is serialization code, but
> > transaction stuff isn't what i want - i'll have to rewrite lot of code to do
> > that transactions..
> >
> > are there better solutions?
> 
> For this very purpose I have used to dump an image of the current running lisp
> that I then restarts upon reboot, but that may not be what you want.
> 
> -- 
> Gisle Sælensminde, Phd student, Scientific programmer
> Computational biology unit, University of Bergen, Norway
> Email: address@hidden | Complicated is easy, simple is hard.

-- 
Camm Maguire                                            address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah