[cl-store-cvs] CVS update: cl-store/doc/cl-store.texi

Sean Ross sross at common-lisp.net
Thu Dec 2 10:32:05 UTC 2004


Update of /project/cl-store/cvsroot/cl-store/doc
In directory common-lisp.net:/tmp/cvs-serv31538/doc

Modified Files:
	cl-store.texi 
Log Message:
Changelog 2004-12-02
Date: Thu Dec  2 11:32:03 2004
Author: sross

Index: cl-store/doc/cl-store.texi
diff -u cl-store/doc/cl-store.texi:1.4 cl-store/doc/cl-store.texi:1.5
--- cl-store/doc/cl-store.texi:1.4	Fri Nov 26 15:35:54 2004
+++ cl-store/doc/cl-store.texi	Thu Dec  2 11:32:02 2004
@@ -148,8 +148,8 @@
 
 The latest cl-store release will always be available from @uref{http://www.common-lisp.net,,cl.net}.
 Download and untar in an appropriate directory then symlink @file{cl-store.asd}
-and @file{cl-store-xml.asd} to a directory on @code{asdf:*central-registry*} (see
-the documentation for asdf for details about setting up asdf).
+to a directory on @code{asdf:*central-registry*} 
+(see the documentation for asdf for details about setting up asdf).
 
 @item CVS
 
@@ -549,7 +549,9 @@
 You can define your own backends in cl-store to do custom object 
 I/O. Theoretically one can add a backend that can do socket
 based communication with any language provided you know the 
-correct format to output objects in.
+correct format to output objects in. If the framework is not 
+sufficient to add your own backend just drop me a line and 
+we will see what we can do about it.
 
 
 @section The Process
@@ -576,7 +578,6 @@
 When storing an object the type code is written down the stream first and then the restoring details for that particular object.
 The @code{get-next-reader} method is then specialized to read the type code and look up the symbol in a hash-table kept
 on the backend. 
-The xml backend outputs no type codes but looks up the symbol by looking at the objects opening tag.
 
 eg. (from the cl-store-backend)
 @lisp
@@ -740,7 +741,7 @@
 @section Known Issues
 @itemize @bullet
 @item  CLISP, OpenMCL, Allegro CL cannot store structure instances.
- at item  Structure definitions are only supported in SBCL.
+ at item  Structure definitions are only supported in SBCL and CMUCL.
 @item  MOP classes aren't supported.
 @item  Due to the fact that function's aren't fully supported CLOS Classes initfunction slot cannot be serialized.
 @end itemize




More information about the Cl-store-cvs mailing list