-;;; the conventional file extension for fasl files on this
-;;; architecture, e.g. "x86f"
-(declaim (type (or simple-string null) *backend-fasl-file-type*))
-(defvar *backend-fasl-file-type* nil)
-
-;;; This is a sort of pun that we inherited from CMU CL. For ordinary,
-;;; non-byte-coded fasl files, the "implementation" is basically the
-;;; CPU. For byte-coded fasl files, the "implementation" is whether
-;;; the data are stored big-endianly or little-endianly.
-(defun backend-byte-fasl-file-implementation ()
- *backend-byte-order*)
+;;; the code for a character which terminates a fasl file header
+(def!constant +fasl-header-string-stop-char-code+ 255)
+
+;;; This value should be incremented when the system changes in such a
+;;; way that it will no longer work reliably with old fasl files. In
+;;; practice, I (WHN) have often forgotten to increment it for CVS
+;;; versions which break binary compatibility. But it certainly should
+;;; be incremented for release versions which break binary
+;;; compatibility.
+(def!constant +fasl-file-version+ 74)
+;;; (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).
+;;; 57: (2005-06-12) Raw slot rearrangement in 0.9.1.38
+;;; 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
+;;; 61: (2005-11-06) Improved source location recording added extra parameters
+;;; to multiple %DEFMUMBLE functions.
+;;; 62: (2005-12-30) Make the count of FASL header counted strings
+;;; a 32-bit value also on 64-bit platforms.
+;;; 63: (2006-01-27) Shuffle storage classes around to reduce the error
+;;; trap information size on RISCy platforms.
+;;; 64: (2006-03-24) New calling convention for unknown-values on x86 and
+;;; x86-64. Also (belatedly) PPC/gencgc, including :gencgc on FPAFF.
+;;; 65: (2006-04-11) Package locking interface changed.
+;;; 66: (2006-05-13) Fopcompiler
+;;; 67: (2006-07-25) Reports on #lisp about 0.9.13 fasls being invalid on
+;;; 0.9.14.something
+;;; 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
+;;; 72: (2006-12-05) Added slot to the primitive function type
+;;; 73: (2007-04-13) Changed a hash function
+;;; 74: (2007-06-05) UNWIND-TO-FRAME-AND-CALL
+
+;;; the conventional file extension for our fasl files
+(declaim (type simple-string *fasl-file-type*))
+(defvar *fasl-file-type* "fasl")