From: Christophe Rhodes Date: Tue, 13 Jul 2004 08:42:01 +0000 (+0000) Subject: 0.8.12.30: X-Git-Url: http://repo.macrolet.net/gitweb/?a=commitdiff_plain;h=accfb3272fece64c18584965f85e975fcc2d6785;p=sbcl.git 0.8.12.30: Build with :sb-package-locks by default ... explain potential workaround for unexpected problems in NEWS, and also trail the likely removal of workaround possibilities in the near future. --- diff --git a/NEWS b/NEWS index ebe8fcc..dbad6fe 100644 --- a/NEWS +++ b/NEWS @@ -1,7 +1,9 @@ changes in sbcl-0.8.13 relative to sbcl-0.8.12: * new feature: SB-PACKAGE-LOCKS. See the "Package Locks" section of - the manual for details; add :SB-PACKAGE-LOCKS in - customize-target-features.lisp to enable them. + the manual for details; for now, package locks can be disabled by + removing :SB-PACKAGE-LOCKS in customize-target-features.lisp, but + if no major problems are found then it is likely that they will be + compiled in unconditionally. * minor incompatible change: as threatened around sbcl-0.8.0, the home package of MOP-related symbols is now SB-MOP, not SB-PCL. The symbols are also exported from SB-PCL for backwards diff --git a/base-target-features.lisp-expr b/base-target-features.lisp-expr index a76ba4a..0dad915 100644 --- a/base-target-features.lisp-expr +++ b/base-target-features.lisp-expr @@ -169,8 +169,11 @@ ;; runtime ; :sb-futex - ;; Package locking support. - ; :sb-package-locks + ;; Support for detection of unportable code (when applied to the + ;; COMMON-LISP package, or SBCL-internal pacakges) or bad-neighbourly + ;; code (when applied to user-level packages), relating to material + ;; alteration to packages or to bindings in symbols in packages. + :sb-package-locks ;; This affects the definition of a lot of things in bignum.lisp. It ;; doesn't seem to be documented anywhere what systems it might apply diff --git a/version.lisp-expr b/version.lisp-expr index 9aea159..19e53bc 100644 --- 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.8.12.29" +"0.8.12.30"