mirror of
git://git.code.sf.net/p/sbcl/sbcl
synced 2026-09-10 07:26:40 -04:00
Working INLINE inside MACROLET for user code. (more or less as per CSR sbcl-devel 2002-12-03) ... change tricky cross-compiled inline functions to source transforms (including adding some functions to the function database) ... use now-working FUNCTION-LAMBDA-EXPRESSION to get the expander function for local macros ... build a complex LAMBDA-WITH-LEXENV for inlining user code (like CMUCL's INLINE-SYNTACTIC-CLOSURE-LAMBDA does) Some miscellaneous frobs ... actually signal a style warning for array code (though it might actually be in currently-dead-but-should-be-alive code) ... actually test the return value in the second half of filesys.test.sh ... minor text adjustments (no more calling this period "early 0.7.x")
22 lines
1.1 KiB
Plaintext
22 lines
1.1 KiB
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 simple 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", with three numeric fields,
|
|
;;; is used for released versions, and a string like "0.6.5.xyzzy",
|
|
;;; with something arbitrary in the fourth field, is used for CVS
|
|
;;; checkins which aren't released. (And occasionally for internal
|
|
;;; versions, especially for internal versions off the main CVS
|
|
;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
|
|
|
|
"0.7.10.10"
|