X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=NEWS;h=b6464e07edfdc0fd57c12d943b3a357606551dc9;hb=b0070d5b0074ef73dc5b2f36205b31d94b8f95a9;hp=d2cc5995dea1ad5f64965c517887ca5c4eddca02;hpb=13719956d7f8944ed88a29998e7f76400f873206;p=sbcl.git diff --git a/NEWS b/NEWS index d2cc599..b6464e0 100644 --- a/NEWS +++ b/NEWS @@ -1127,39 +1127,85 @@ changes in sbcl-0.7.4 relative to sbcl-0.7.3: |AB|, instead of A as it used to. changes in sbcl-0.7.5 relative to sbcl-0.7.4: - * SBCL now runs on the Tru64 (aka OSF/1) operating system on the - Alpha architecture. - * SBCL now builds with OpenMCL (version 0.11+patches) as the + * SBCL now builds with OpenMCL (version 0.12) as the cross-compilation host; also, more progress has been made toward bootstrapping under CLISP. - * bug 140 fixed: redefinition of classes with different supertypes - is now reflected in the type hierarchy. (thanks to Pierre Mai) - * bug 158 fixed: the compiler can now deal with integer loop + * SBCL now runs on the Tru64 (aka OSF/1) operating system on the + Alpha architecture. + * bug 158 fixed: The compiler can now deal with integer loop increments different from 1; fixing this turned out also to fix bug 164. * bug 169 fixed: no more bogus warnings about using lexical bindings - despite the presence of perfectly good SPECIAL declarations. (thanks + despite the presence of perfectly good SPECIAL declarations (thanks to David Lichteblau) - * bug 175 fixed: more-closely-ANSI CHANGE-CLASS function, now + * bug 175 fixed: CHANGE-CLASS is now more ANSI-conforming, accepting initargs. (thanks to Espen Johnsen and Pierre Mai) * bug 179 fixed: DIRECTORY can now deal with filenames with pattern characters in them. + * bug 180 fixed: Method combination specifications no longer ignore + the :MOST-SPECIFIC-LAST option. (thanks to Pierre Mai) * bug fix: Structure type predicate functions now check their argument count as they should. - * bug fix: classes with :METACLASS STRUCTURE-CLASS now print + * bug fix: Classes with :METACLASS STRUCTURE-CLASS now print correctly. (thanks to Pierre Mai) * minor incompatible change: The --noprogrammer option is deprecated - in favor of the new name --disable-debugger option, which takes - effect at a slightly different time at startup (so that e.g. - handling of errors in --sysinit and --userinit files will be affected - differently). The SB-EXT:DISABLE-DEBUGGER and SB-EXT:ENABLE-DEBUGGER - functions have been added to allow this functionality to be controlled - from ordinary Lisp code. (ENABLE-DEBUGGER should help people like the - Debian maintainers, who might want to run non-interactive scripts to + in favor of the new --disable-debugger option, which is very similar. + (The major difference is that it takes effect at a slightly different + time at startup, causing handling of errors in --sysinit and + --userinit files will be affected differently.) The + SB-EXT:DISABLE-DEBUGGER and SB-EXT:ENABLE-DEBUGGER functions have + been added to allow this functionality to be controlled from ordinary + Lisp code. (ENABLE-DEBUGGER should help people like the Debian + maintainers, who might want to run non-interactive scripts to build SBCL cores which will later be used interactively.) * minor incompatible change: The LOAD function no longer, when given - a wild pathname to load, loads all files matching that pathname; - instead, an error of type FILE-ERROR is signalled. + a wild pathname to load, loads all files matching that pathname. + Instead, an error of type FILE-ERROR is signalled. + +changes in sbcl-0.7.6 relative to sbcl-0.7.5: + * bug fix: Floating point exceptions are treated much more + consistently on the x86/Linux and PPC/Linux platforms. + * Array initialization with :INITIAL-ELEMENT is now much faster for + cases when the compiler cannot open code the array creation, but + does know what the UPGRADED-ARRAY-ELEMENT-TYPE will be. General + array accesses have also seen a speed increase. + * bug fix: LOAD :IF-DOES-NOT-EXIST NIL now works when file type is + specified. (This was at the root of some bad interactions between + SBCL and ILISP: thanks to Gregory Wright for diagnosing this and + reporting the bug.) + * bug fix: Internal error arguments for undefined functions are now + computed correctly on the PPC/Linux platform. + * bug fix: Bad &REST syntax is now checked correctly. (thanks to + Raymond Toy's patch for CMU CL) + * Support for the Solaris 9 operating environment has been included + (thanks to Daniel Merritt) + * A very ugly but hopefully complete draft of the missing FFI chapter + of the manual has been created by reformatting the corresponding + CMU CL manual chapter into (currently very ugly and incoherent) + DocBook and bringing it up to date for SBCL behavior. Thus, the + manual is now essentially complete, at least by my extreme + once-and-only-once standards, whereby it's acceptable to refer to + the doc strings of SB-EXT functions as the primary documentation. + * The fasl file version number has changed again, due to cleanup of + (user-invisible) bitrotted stuff. (E.g. *!INITIAL-FDEFN-OBJECTS* + is no longer a static symbol.) + +changes in sbcl-0.7.7 relative to sbcl-0.7.6: + * fixed bug 189: The compiler now respects NOTINLINE declarations for + functions declared in FLET and LABELS. (I.e. "LET conversion" is + suppressed.) Also now that the compiler is looking at declarations + in the environment, it checks optimization declarations as well, + and suppresses inlining when (> DEBUG SPEED). + * More fixes have been made to treatment of floating point exception + treatment and other Unix signals. In particular, floating point + exceptions no longer cause Bus errors on the SPARC/Linux platform. + * The detection and handling of control stack exhaustion (infinite + or very deeply nested recursion) has changed. Stack exhaustion + detection is now done by write-protecting pages at the OS level + and applies at all optimization settings; when found, a + SB-KERNEL:CONTROL-STACK_EXHAUSTED condition (subclass of + STORAGE-CONDITION) is signalled, so stack exhaustion can no longer + be caught using IGNORE-ERRORS planned incompatible changes in 0.7.x: * When the profiling interface settles down, maybe in 0.7.x, maybe