X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=NEWS;h=00e8230013a7bd315df5bf43b50c8a51684ed22c;hb=b8f63d9b4e978bec3bfc1f4fc471e5ed946781fd;hp=e128109cd22831a74fcb502967d22000c3f79dbd;hpb=8eb659eee63e989f2f3da5673c3ac00a6712f567;p=sbcl.git

diff --git a/NEWS b/NEWS
index e128109..00e8230 100644
--- a/NEWS
+++ b/NEWS
@@ -623,12 +623,23 @@ changes in sbcl-0.6.10 relative to sbcl-0.6.9:
   and there's no compelling reason to try to stretch the standard
   to allow two different extensions.) Instead, byte-compiled files
   default to the same extension as native-compiled files.
-?? #'(SETF DOCUMENTATION) is now defined.
+* Fasl file format version numbers have increased again, because
+  a rearrangement of internal implementation packages made some 
+  dumped symbols in old fasl files unreadable in new cores.
+* DECLARE/DECLAIM/PROCLAIM logic is more nearly ANSI in general, with
+  many fewer weird special cases.
 * Bug #17 (differing COMPILE-FILE behavior between logical and 
   physical pathnames) has been fixed, and some related misbehavior too,
   thanks to a patch from Martin Atzmueller.
+* Bug #30 (reader problems) is gone, thanks to a CMU CL patch
+  by Tim Moore, ported to SBCL by Martin Atzmueller.
+* Martin Atzmueller fixed several filesystem-related problems,
+  including bug #36, in part by porting CMU CL patches, which were
+  written in part by Paul Werkowski.
 * More compiler warnings in src/runtime/ are gone, thanks to 
-  patches from Martin Atzmueller.
+  more patches from Martin Atzmueller.
+* Martin Atzmueller pointed out that bug 37 was fixed by his patches
+  some time ago.
 
 planned incompatible changes in 0.7.x:
 * The debugger prompt sequence now goes "5]", "5[2]", "5[3]", etc.
@@ -636,3 +647,7 @@ planned incompatible changes in 0.7.x:
   instead of the old "5]", "5]]", "5]]]" sequence. (I was motivated
   to do this when ILISP and SBCL got into arguments which left me
   deeply nested in the debugger.)
+* When the profiling interface settles down, it might impact TRACE.
+  They both encapsulate functions, and it's not clear yet how
+  e.g. UNPROFILE will interact with TRACE and UNTRACE. (This shouldn't
+  matter, though, unless you are using profiling.)