0.pre7.120:

[sbcl.git] / NEWS

diff --git a/NEWS b/NEWS
index 0336a7a..426f7a5 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -899,6 +899,7 @@ changes in sbcl-0.7.0 relative to sbcl-0.6.13:
   ** bug in the optimization of ARRAY-ELEMENT-TYPE
   ** argument ordering in FIND with :TEST option
   ** mishandled package designator argument in APROPOS-LIST
   ** bug in the optimization of ARRAY-ELEMENT-TYPE
   ** argument ordering in FIND with :TEST option
   ** mishandled package designator argument in APROPOS-LIST

+  ** various problems in the backquote readmacro

   He also pointed out some bogus old entries in BUGS, and fixed 
   a number of bugs which came into existence in the pre7 branch
   (internal to the CVS repository), so that they never showed
   He also pointed out some bogus old entries in BUGS, and fixed 
   a number of bugs which came into existence in the pre7 branch
   (internal to the CVS repository), so that they never showed

@@ -914,16 +915,23 @@ changes in sbcl-0.7.0 relative to sbcl-0.6.13:
   ILISP and SBCL left me very deeply nested in the debugger. In the
   short term, this change will probably provoke more ILISP/SBCL 
   squabbles, but hopefully it will be an improvement in the long run.)
   ILISP and SBCL left me very deeply nested in the debugger. In the
   short term, this change will probably provoke more ILISP/SBCL 
   squabbles, but hopefully it will be an improvement in the long run.)

-?? minor incompatible change: The default output representation for
-  unprintable ASCII characters which, unlike e.g. #\Newline, don't
-  have names defined in the ANSI Common Lisp standard, is now based
-  on their ASCII symbolic names: #\Nul, #\Soh, #\Stx, etc.
+* minor incompatible change: The CHAR-NAME of unprintable ASCII
+  characters which, unlike e.g. #\Newline and #\Tab, don't have names
+  specified in the ANSI Common Lisp standard, is now based on their
+  ASCII symbolic names (#\Nul, #\Soh, #\Stx, etc.) The old CMU CL
+  names (#\Null, #\^a, #\^b, etc.) are still accepted by NAME-CHAR.

 ?? Old operator names in the style DEF-FOO are now deprecated in
   favor of new corresponding names DEFINE-FOO, for consistency with
   the naming convention used in the ANSI standard (DEFSTRUCT, DEFVAR,
   DEFINE-CONDITION, DEFINE-MODIFY-MACRO..). This mostly affects
   internal symbols, but a few supported extensions like
   SB-ALIEN:DEF-ALIEN-FUNCTION are also affected.
 ?? Old operator names in the style DEF-FOO are now deprecated in
   favor of new corresponding names DEFINE-FOO, for consistency with
   the naming convention used in the ANSI standard (DEFSTRUCT, DEFVAR,
   DEFINE-CONDITION, DEFINE-MODIFY-MACRO..). This mostly affects
   internal symbols, but a few supported extensions like
   SB-ALIEN:DEF-ALIEN-FUNCTION are also affected.

+* minor incompatible change (part of a bug fix by Christophe Rhodes
+  to DIRECTORY behavior): DIRECTORY no longer implicitly promotes
+  NIL slots of its pathname argument to :WILD, and in particular
+  asking for the contents of a directory, which you used to be able
+  to do without explicit wildcards, e.g. (DIRECTORY "/tmp/"), 
+  now needs explicit wildcards, e.g. (DIRECTORY "/tmp/*.*").

 * minor incompatible change: DEFINE-ALIEN-FUNCTION (also known by 
   the old deprecated name DEF-ALIEN-FUNCTION) now does DECLAIM FTYPE
   for the defined function, since declaiming return types involving
 * minor incompatible change: DEFINE-ALIEN-FUNCTION (also known by 
   the old deprecated name DEF-ALIEN-FUNCTION) now does DECLAIM FTYPE
   for the defined function, since declaiming return types involving