X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=NEWS;h=b6e2a515350de8daa25418073ea983fedb4489ad;hb=4fc9d21ae1d8a6a2f8ff70f589d5da103203de13;hp=e2a01ea20d6a89f6fd627fe0536b16c6b531a30e;hpb=f188d1c6cdcb9d9aa117baf617c70a2933fa1c60;p=sbcl.git

diff --git a/NEWS b/NEWS
index e2a01ea..b6e2a51 100644
--- a/NEWS
+++ b/NEWS
@@ -597,13 +597,69 @@ changes in sbcl-0.6.9 relative to sbcl-0.6.8:
 * Martin Atzmueller also fixed ROOM, so that it no longer fails with an
   undefined function error.
 * gave up on fixing bug 3 (forbidden-by-ANSI warning for type mismatch
-  in structure slot initforms) for now, wrote workaround instead:-|
+  in structure slot initforms) for now, documented workaround instead:-|
 * fixed bug 4 (no WARNING for DECLAIM FTYPE of slot accessor function)
 * fixed bug 5: added stubs for various Gray stream functions called
   in the not-a-CL:STREAM case, so that even when Gray streams aren't
   installed, at least appropriate type errors are generated
+* fixed bug 8: better reporting of various PROGRAM-ERRORs
+* fixed bug 9: IGNORE and IGNORABLE now work reasonably and more
+  consistently in DEFMETHOD forms. 
 * removed bug 21 from BUGS, since Martin Atzmueller points out that 
   it doesn't seem to affect SBCL after all
+* The C runtime system now builds with better optimization and many
+  fewer warnings, thanks to lots of cleanups by Martin Atzmueller.
+
+changes in sbcl-0.6.10 relative to sbcl-0.6.9:
+
+* A patch from Martin Atzmueller seems to have solved the SIGINT
+  problem, and as far as we know, signal-handling now works cleanly.
+  (If you find any new bugs, please report them!)
+* The system no longer defaults Lisp source file names to types
+  ".l", ".cl", or ".lsp", but only to ".lisp". 
+* The compiler no longer uses special default file extensions for
+  byte-compiled code. (The ANSI definition of COMPILE-FILE-PATHNAME
+  seems to expect a single default extension for all compiled code,
+  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.
+* 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 
+  more patches from Martin Atzmueller.
+* Martin Atzmueller pointed out that bug 37 was fixed by his patches
+  some time ago.
+
+changes in sbcl-0.6.11 relative to sbcl-0.6.10:
+* The Gray subclassable streams extension now works, thanks to a 
+  patch from Martin Atzmueller.
+* The full LOAD-FOREIGN extension (not just the primitive
+  LOAD-FOREIGN-1) now works, thanks to a patch from Martin Atzmueller.
+* The default behavior of RUN-PROGRAM has changed. Now, unlike CMU CL
+  but like most other programs, it defaults to copying the Unix
+  environment from the original process instead of starting the
+  new process in an empty environment.
+* Extensions which manipulate the Unix environment now support
+  an :ENVIRONMENT keyword option which doesn't smash case or 
+  do other bad things. The CMU-CL-style :ENV option is retained
+  for porting convenience.
+* LOAD-FOREIGN (and LOAD-1-FOREIGN) now support logical pathnames,
+  as per Daniel Barlow's suggestion and Martin Atzmueller's patch
+* DESCRIBE now works on structure objects again.
+* Fasl file format version numbers have increased again, because
+  support for the Gray streams extension changes the format of the
+  system's stream objects.
 
 planned incompatible changes in 0.7.x:
 * The debugger prompt sequence now goes "5]", "5[2]", "5[3]", etc.
@@ -611,3 +667,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.)