mirror of
git://git.code.sf.net/p/sbcl/sbcl
synced 2026-09-10 07:26:40 -04:00
8eb659eee6
BACKEND-BYTE-FASL-FILE-TYPE goes away as per 0.6.9.4. Simplify TRY-DEFAULT-TYPES and friends by using single default types instead of lists of default types. more work on bug #17, loosely based on MNA's patch; still broke started tests/pathnames.impure.lisp failed to fix cross-compilation under CMU CL
19 lines
914 B
Plaintext
19 lines
914 B
Plaintext
;;; This is the master value for LISP-IMPLEMENTATION-VERSION. It's
|
|
;;; separated into its own file here so that it's easy for
|
|
;;; text-munging make-ish or cvs-ish scripts to find and tweak it. For
|
|
;;; the convenience of such scripts, only a trivial subset of Lisp
|
|
;;; reader syntax should be used here: semicolon-delimited comments,
|
|
;;; possible blank lines or other whitespace, and a single
|
|
;;; double-quoted string value alone on its own line.
|
|
;;;
|
|
;;; ANSI says LISP-IMPLEMENTATION-VERSION can be NIL "if no
|
|
;;; appropriate and relevant result can be produced", but as long as
|
|
;;; we control the build, we can always assign an appropriate and
|
|
;;; relevant result, so this must be a string, not NIL.
|
|
;;;
|
|
;;; Conventionally a string like "0.6.6" is used for released
|
|
;;; versions, and a string like "0.6.5.12" is used for versions which
|
|
;;; aren't released but correspond only to CVS tags or snapshots.
|
|
|
|
"0.6.9.5"
|