From: Nikodemus S. <de...@us...> - 2006-06-09 20:59:53
|
Update of /cvsroot/sbcl/sbcl In directory sc8-pr-cvs8.sourceforge.net:/tmp/cvs-serv2843 Modified Files: NEWS base-target-features.lisp-expr version.lisp-expr Log Message: 0.9.13.36: global policy / null-lexenv confusion fix * Do not store the global policy in null-lexenv, but include it in subsequent lexenvs. Fixes visibility of global policy in LOCALLY and MACROLET. * Also actually enable the SB-LDB in default build instead of just providing the framework to make this a good idea. (Accidentally left out from from 0.9.13.33) Index: NEWS =================================================================== RCS file: /cvsroot/sbcl/sbcl/NEWS,v retrieving revision 1.1012 retrieving revision 1.1013 diff -u -d -r1.1012 -r1.1013 --- NEWS 9 Jun 2006 17:07:37 -0000 1.1012 +++ NEWS 9 Jun 2006 20:59:44 -0000 1.1013 @@ -15,6 +15,8 @@ * minor incompatible change: the :SB-LDB feature is now enabled by default, and DISABLE-DEBUGGER and ENABLE-DEBUGGER also affect the low-level debugger. + * bug fix: global optimization policy was not visible in LOCALLY and + MACROLET forms. * bug fix: class objects can be used as specializers in methods. (reported by Pascal Costanza) * bug fix: native unparsing of pathnames with :DIRECTORY NIL failed Index: base-target-features.lisp-expr =================================================================== RCS file: /cvsroot/sbcl/sbcl/base-target-features.lisp-expr,v retrieving revision 1.39 retrieving revision 1.40 diff -u -d -r1.39 -r1.40 --- base-target-features.lisp-expr 3 Jun 2006 20:26:52 -0000 1.39 +++ base-target-features.lisp-expr 9 Jun 2006 20:59:44 -0000 1.40 @@ -107,11 +107,13 @@ ;; readtable configured so that the system sources can be read. ; :sb-show - ;; Build SBCL with the old CMU CL low level debugger, "ldb". If are - ;; aren't messing with SBCL at a very low level (e.g., trying to - ;; diagnose GC problems, or trying to debug assembly code for a port - ;; to a new CPU) you shouldn't need this. - ; :sb-ldb + ;; Build SBCL with the old CMU CL low level debugger, "ldb". In the + ;; ideal world you would not need this unless you are messing with + ;; SBCL at a very low level (e.g., trying to diagnose GC problems, or + ;; trying to debug assembly code for a port to a new CPU). However, + ;; experience shows that sooner or later everyone lose()'s, in which + ;; case SB-LDB can at least provide an informative backtrace. + :sb-ldb ;; This isn't really a target Lisp feature at all, but controls ;; whether the build process produces an after-xc.core file. This Index: version.lisp-expr =================================================================== RCS file: /cvsroot/sbcl/sbcl/version.lisp-expr,v retrieving revision 1.2863 retrieving revision 1.2864 diff -u -d -r1.2863 -r1.2864 --- version.lisp-expr 9 Jun 2006 17:07:38 -0000 1.2863 +++ version.lisp-expr 9 Jun 2006 20:59:44 -0000 1.2864 @@ -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.13.35" +"0.9.13.36" |