0.9.16.26:

	memory crutch for middle-aged maintainers: repeated NS's
		explanation in 0.9.16.25 commit message as comment
		above the change

diff --git a/src/compiler/globaldb.lisp b/src/compiler/globaldb.lisp
index 4aefaff..1f1eeb5 100644 (file)
--- a/src/compiler/globaldb.lisp
+++ b/src/compiler/globaldb.lisp
@@ -789,13 +789,17 @@
   new-value)
 #!-sb-fluid
 (progn
+  ;; Not all xc hosts are happy about SETF compiler macros: CMUCL 19
+  ;; does not accept them at all, and older SBCLs give a full warning.
+  ;; So the easy thing is to hide this optimization from all xc hosts.
   #-sb-xc-host
   (define-compiler-macro (setf info) (&whole whole
                                              new-value
                                              class
                                              type
                                              name
-                                             &optional (env-list nil env-list-p))
+                                             &optional (env-list nil
+                                                                 env-list-p))
     ;; Constant CLASS and TYPE is an overwhelmingly common special case,
     ;; and we can resolve it much more efficiently than the general
     ;; case.

diff --git a/version.lisp-expr b/version.lisp-expr
index a966c58..041ec82 100644 (file)
--- a/version.lisp-expr
+++ b/version.lisp-expr
@@ -17,4 +17,4 @@
 ;;; 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.9.16.25"
+"0.9.16.26"