From 9ef06faae78cc88c38b13af6593222a13e332ee0 Mon Sep 17 00:00:00 2001 From: William Harold Newman Date: Sat, 21 Sep 2002 13:32:19 +0000 Subject: [PATCH] 0.7.7.37: incremented FASL-FILE-VERSION --- NEWS | 9 ++++++++- package-data-list.lisp-expr | 2 +- src/code/early-fasl.lisp | 4 +++- version.lisp-expr | 2 +- 4 files changed, 13 insertions(+), 4 deletions(-) diff --git a/NEWS b/NEWS index 64a04a7..83dade2 100644 --- a/NEWS +++ b/NEWS @@ -1277,7 +1277,14 @@ changes in sbcl-0.7.8 relative to sbcl-0.7.7: in several ways. (thanks to Alexey Dejneka) * fixed bug 181: compiler checks validity of user supplied type specifiers - * functions, which must signal errors, are no longer flushable + * cleaned up code flushing in optimization: Function calls which + should signal errors for safety purposes (e.g. which ANSI says + should signal errors when their arguments are of incorrect type) + are no longer optimized away. + * incremented fasl file version number, because changes in the + implementation of sequence functions like COERCE have old + internal utility functions like COERCE-TO-SIMPLE-VECTOR (used + in old inline expansions) to become undefined planned incompatible changes in 0.7.x: * When the profiling interface settles down, maybe in 0.7.x, maybe diff --git a/package-data-list.lisp-expr b/package-data-list.lisp-expr index ca4183e..1c4f69a 100644 --- a/package-data-list.lisp-expr +++ b/package-data-list.lisp-expr @@ -1006,7 +1006,7 @@ is a good idea, but see SB-SYS re. blurring of boundaries." "CODE-INSTRUCTIONS" "COERCE-TO-BIT-VECTOR" "COERCE-TO-FUN" "COERCE-TO-LEXENV" "COERCE-TO-LIST" "COERCE-TO-SIMPLE-STRING" - "COERCE-TO-SIMPLE-VECTOR" "COERCE-TO-VECTOR" + "COERCE-TO-VECTOR" "*COLD-INIT-COMPLETE-P*" "COMPLEX-DOUBLE-FLOAT-P" "COMPLEX-FLOAT-P" "COMPLEX-LONG-FLOAT-P" diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp index 87dd4e6..be855f6 100644 --- a/src/code/early-fasl.lisp +++ b/src/code/early-fasl.lisp @@ -42,7 +42,7 @@ ;;; versions which break binary compatibility. But it certainly should ;;; be incremented for release versions which break binary ;;; compatibility. -(def!constant +fasl-file-version+ 31) +(def!constant +fasl-file-version+ 32) ;;; (record of versions before 0.7.0 deleted in 0.7.1.41) ;;; 23 = sbcl-0.7.0.1 deleted no-longer-used EVAL-STACK stuff, ;;; causing changes in *STATIC-SYMBOLS*. @@ -61,6 +61,8 @@ ;;; 31: (2002-08-14) changed encoding of PCL internal MAKE-INSTANCE ;;; function names so they're insensitive to whether the class name ;;; is currently external to its package +;;; 32: (2002-09-21) changes in implementation of sequence functions, +;;; causing old utility functions like COERCE-TO-SIMPLE-VECTOR to go away ;;; 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 683151d..0dc4453 100644 --- a/version.lisp-expr +++ b/version.lisp-expr @@ -18,4 +18,4 @@ ;;; internal versions off the main CVS branch, it gets hairier, e.g. ;;; "0.pre7.14.flaky4.13".) -"0.7.7.36" +"0.7.7.37" -- 1.7.10.4