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

[Sean Ross]

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

Modified Files:
	cl-store.texi 
Log Message:
Changelog 2005-05-06
Date: Fri May  6 16:19:31 2005
Author: sross

Index: cl-store/doc/cl-store.texi
diff -u cl-store/doc/cl-store.texi:1.10 cl-store/doc/cl-store.texi:1.11
--- cl-store/doc/cl-store.texi:1.10	Thu Mar 24 09:25:20 2005
+++ cl-store/doc/cl-store.texi	Fri May  6 16:19:30 2005
@@ -211,7 +211,7 @@
 @anchor{Variable *store-used-packages*}
 @vindex *store-used-packages*
 @deftp {Variable} *store-used-packages* @emph{Default NIL}
-The variable determines the how packages on a package use
+The variable determines how packages on a package use
 list will be serialized. If non-nil the the package will
 be fully serialized, otherwise only the name will be stored.
 @end deftp
@@ -278,8 +278,9 @@
 
 
 @anchor{Function find-backend}
- at deffn {Function} find-backend name
-Returns the backend named by @emph{name} or nil if it does not exist.
+ at deffn {Function} find-backend name &optional (errorp nil)
+Return backup called @emph{name}. If there is no such backend NIL is returned 
+if @emph{errorp} is false, otherwise an error is signalled.
 @end deffn
 
 @anchor{Function caused-by}
@@ -380,7 +381,7 @@
 Registers @emph{name} under the code @emph{code} into the cl-store-backend. 
 The backend will use this mapping when restoring values. 
 Will signal an error if code is already registered and @emph{errorp} is not NIL.
-Currently codes 1 through 33 are in use.
+Currently codes 1 through 35 are in use.
 @end deffn
 
 @anchor{Function output-type-code}
@@ -754,6 +755,16 @@
 @item  Due to the fact that function's aren't fully supported CLOS Classes initfunction slot cannot be serialized.
 @end itemize
 
+
+ at section Regarding String Serialization
+Users are required to be extremely careful when serializing strings from one
+lisp implementation to another since the array-element-type will be tracked
+for strings and the Hyperspec does not specify an upper limit for base-chars.
+This can be a problem if you serialize a simple-base-string containing wide 
+characters, in an implementation which specifies no limit on base-char, 
+to an implementation with a limit.
+If you have a solution I would be happy to hear it.
+
 @node Credits
 @chapter Credits
 Thanks To
@@ -762,6 +773,7 @@
 @item Alain Picard : Structure Storing and support for Infinite Floats for Lispworks.
 @item Robert Sedgewick: Package Imports for OpenMCL and suggesting Multiple Backends.
 @item Thomas Stenhaug: Comprehensive package storing and miscellaneous improvements.
+ at item Killian Sprotte: Type specification fixups.
 @end itemize
 
 @node Index