0.9.5.85:

        Here is +FASL-FILE-VERSION+, coming downstairs now, bump, bump, bump,
        on the back of his head, behind Christopher Robin.

diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp
index 89ad9be..b1734d2 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+ 59)
+(def!constant +fasl-file-version+ 60)
 ;;; (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
@@ -125,6 +125,7 @@
 ;;; 58: (2005-08-16) Multiple incompatible changes between 0.9.3 and 0.9.3.60
 ;;; 59: (2005-09-18) METAOBJECT implementation, removal of INSTANCE and
 ;;;     FUNCALLABLE-INSTANCE classes.
+;;; 60: (2005-10-24) Bumped for 0.9.6
 
 ;;; 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 fbeae3f..aac1954 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.9.5.84"
+"0.9.5.85"