4:35:04beachemaczen: I am guessing it is pretty messy in a system (OS + Common Lisp implementation) that was not meant for it in the first place.
4:36:54beachemaczen: You may consider looking at this one: https://github.com/robert-strandh/Clobber
4:49:15White_Flameemaczen: the biggest issues to deal with are serializing function objects and dealing with multiple references to shared objects
4:49:49White_Flamedifferent libraries deal with such things in different ways. The only "standard" way persistence happens is saving your lisp image, which isn't even in the spec
4:54:21beachemaczen: If you can describe your needs, that might make it easier to give you advice.
10:19:55rk[ghost]that brings up an interesting thought.. what do you all use for serialization of function objects?
11:08:25_deathgenerally you avoid serializing those.. but see http://www.discontinuity.info/~pkhuong/common-cold/
11:40:26phoegenerally you serialize those by (if at all) capturing their source code at compile time and storing the source code, then compiling it again during deserialization
11:40:52phoesince that's the only semi-portable way that is standard-compliant AFAIK