0.8.1.47:

	A +FASL-FILE-VERSION+ a month reduces bug hunth.

diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp
index e63caf7..4cf73e9 100644 (file)
--- a/src/code/early-fasl.lisp
+++ b/src/code/early-fasl.lisp
@@ -76,7 +76,7 @@
 ;;; versions which break binary compatibility. But it certainly should
 ;;; be incremented for release versions which break binary
 ;;; compatibility.
-(def!constant +fasl-file-version+ 42)
+(def!constant +fasl-file-version+ 43)
 ;;; (record of versions before 2003 deleted in 2003-04-26/0.pre8.107 or so)
 ;;; 38: (2003-01-05) changed names of internal SORT machinery
 ;;; 39: (2003-02-20) in 0.7.12.1 a slot was added to
@@ -86,6 +86,10 @@
 ;;;     and -SB-THREAD builds
 ;;; 42: (2003-05-22) %NAME slot changed to NAME in
 ;;;     DEFSTRUCT-SLOT-DESCRIPTION
+;;; 43: (2003-07-18) Something could easily have changed incompatibly in
+;;;     recent maintenance, e.g. from (VECTOR NIL)-as-string support.
+;;;     (And experimental results suggest that compatibility was broken
+;;;     between about 0.8.1.29 and 0.8.1.39.)
 
 ;;; the conventional file extension for our fasl files
 (declaim (type simple-string *fasl-file-type*))

diff --git a/version.lisp-expr b/version.lisp-expr
index ecf4f07..5e52b29 100644 (file)
--- a/version.lisp-expr
+++ b/version.lisp-expr
@@ -17,4 +17,4 @@
 ;;; checkins which aren't released. (And occasionally for internal
 ;;; versions, especially for internal versions off the main CVS
 ;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"0.8.1.46"
+"0.8.1.47"