0.8.5.33:

	bumped .fasl file version number as per Tim Daly Jr.
		incompatibility report on sbcl-devel 2003-11-09

diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp
index 5e331ba..8719750 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+ 45)
+(def!constant +fasl-file-version+ 46)
 ;;; (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
@@ -100,6 +100,8 @@
 ;;;     .fasl files could never possibly ever refer to the SB-C
 ;;;     CONTINUATION-related data types which were changed 
 ;;;     incompatibly in 0.8.3.62.
+;;; 46: (2003-11-11) Tim Daly, Jr. (and Christophe Rhodes) reported
+;;;     .fasl incompatibility on sbcl-devel 2003-11-09.
 
 ;;; 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 8acc280..d4eb384 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.5.32"
+"0.8.5.33"