From 8e95c816592918670cb08d4b2c24b0ff03f55ea9 Mon Sep 17 00:00:00 2001 From: Juho Snellman Date: Sun, 19 Nov 2006 01:47:32 +0000 Subject: [PATCH] 0.9.18.59: Bump fasl-file-version (at least CLOS calling convention changes). --- src/code/early-fasl.lisp | 3 ++- version.lisp-expr | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp index 3511019..93eb465 100644 --- 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+ 70) +(def!constant +fasl-file-version+ 71) ;;; (description of versions before 0.9.0.1 deleted in 0.9.17) ;;; 56: (2005-05-22) Something between 0.9.0.1 and 0.9.0.14. My money is ;;; on 0.9.0.6 (MORE CASE CONSISTENCY). @@ -100,6 +100,7 @@ ;;; 68: (2006-08-14) changed number of arguments of LOAD-DEFMETHOD ;;; 69: (2006-08-17) changed validity of various initargs for methods ;;; 70: (2006-09-13) changes to *PSEUDO-ATOMIC* on x86 and x86-64 +;;; 71: (2006-11-19) CLOS calling convention changes ;;; 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 8e46220..8e200e9 100644 --- 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.18.58" +"0.9.18.59" -- 1.7.10.4