0.8.13.58:

[sbcl.git] / src / code / early-fasl.lisp

diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp
index e63caf7..029d24a 100644 (file)
--- a/src/code/early-fasl.lisp
+++ b/src/code/early-fasl.lisp
@@ -35,7 +35,7 @@
 
 (macrolet ((define-fasl-format-features ()
              (let (;; master value for *F-P-A-F-F*
-                  (fpaff '(:sb-thread)))
+                  (fpaff '(:sb-thread :sb-package-locks)))
               `(progn
                  ;; a list of *(SHEBANG-)FEATURES* flags which affect
                  ;; binary compatibility, i.e. which must be the same
@@ -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+ 42)
+(def!constant +fasl-file-version+ 51)
 ;;; (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
@@ -86,6 +86,30 @@
 ;;;     and -SB-THREAD builds
 ;;; 42: (2003-05-22) %NAME slot changed to NAME in
 ;;;     DEFSTRUCT-SLOT-DESCRIPTION
+;;; 43: (2003-07-18) Something could easily have changed incompatibly in
+;;;     recent maintenance, e.g. from (VECTOR NIL)-as-string support.
+;;;     (And experimental results suggest that compatibility was broken
+;;;     between about 0.8.1.29 and 0.8.1.39.)
+;;; 44: (2003-08-25) various changes leading up to 0.8.3
+;;;     <dan`b> what happened this month to stalate the fasls?
+;;;     <Krystof_> I think I renumbered everything again
+;;;     <Krystof_> simple-array-unsigned-byte-7, probably
+;;;     <Krystof_> (thanks to pfdietz)
+;;; 45: (2003-10-02) I (WHN) incremented the version for the 0.8.4 
+;;;     release because I couldn't immediately convince myself that
+;;;     .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.
+;;; 47: (2003-11-30) Static variables were rearranged in 0.8.6.11.
+;;; 48: (2004-03-01) Renumbered all the widetags to allow for more
+;;;     microefficiency in sbcl-0.8.8.10
+;;; 49: (2004-05-04) Changed implementation of DEFFOO macros and the
+;;;     functions they expand to.
+;;; 50: (2004-05-20) Changed %COMPILER-DEFUN signature again.
+;;; 51: (2004-07-24) Package locks (SBCL 0.8.12.7) changed signature of
+;;;     %DEFPACKAGE.
 
 ;;; the conventional file extension for our fasl files
 (declaim (type simple-string *fasl-file-type*))
@@ -122,9 +146,6 @@
              :initial-element (lambda ()
                                 (error "corrupt fasl file: losing FOP"))))
 \f
-;;;; other miscellaneous loading-related stuff
-
-\f
 ;;;; variables
 
 (defvar *load-depth* 0
@@ -136,15 +157,4 @@
 (defvar *fasl-input-stream*)
 (declaim (type ansi-stream *fasl-input-stream*))
 
-(defvar *load-print* nil
-  #!+sb-doc
-  "the default for the :PRINT argument to LOAD")
-(defvar *load-verbose* nil
-  ;; Note that CMU CL's default for this was T, and ANSI says it's
-  ;; implementation-dependent. We choose NIL on the theory that it's
-  ;; a nicer default behavior for Unix programs.
-  #!+sb-doc
-  "the default for the :VERBOSE argument to LOAD")
-
 (defvar *load-code-verbose* nil)
-