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
"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"
;;; 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*.
;;; 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*))
;;; 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"