X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=NEWS;h=63f6ec5fa8fa556da0a86e1f7eaf6bf9c575d14c;hb=6c765578c8dc4bcc7798e37c9918715f198b30da;hp=8c22dbda68f9727303f494ef953dcf7bbb706993;hpb=e58b011bbe611f10fbc316eea0a3e205c3e40ac7;p=sbcl.git diff --git a/NEWS b/NEWS index 8c22dbd..63f6ec5 100644 --- a/NEWS +++ b/NEWS @@ -642,6 +642,30 @@ changes in sbcl-0.6.10 relative to sbcl-0.6.9: some time ago. changes in sbcl-0.6.11 relative to sbcl-0.6.10: +* Martin Atzmueller pointed out that bugs #9 and #25 are gone in + current SBCL. +* bug 34 fixed by Martin Atzmueller: dumping/loading instances works + better +* fixed bug 40: TYPEP, SUBTYPEP, UPGRADED-ARRAY-ELEMENT-TYPE, + and UPGRADED-COMPLEX-PART-TYPE now work better with of compound + types built from undefined types, e.g. '(VECTOR SOME-UNDEF-TYPE). +* DESCRIBE now works on structure objects again. +* Most function call argument type mismatches are now handled as + STYLE-WARNINGs instead of full WARNINGs, since the compiler doesn't + know whether the function will be redefined before the call is + executed. (The compiler could flag local calls with full WARNINGs, + as per the ANSI spec "3.2.2.3 Semantic Constraints", but right now + it doesn't keep track of enough information to know whether calls + are local in this sense.) +* Compiler output is now more verbose, with messages truncated + later than before. (There should be some supported way for users + to override the default verbosity, but I haven't decided how to + provide it yet, so this behavior is still controlled by the internal + SB-C::*COMPILER-ERROR-PRINT-FOO* variables in + src/compiler/ir1util.lisp.) +* Fasl file format version numbers have increased again, because + support for the Gray streams extension changes the layout of the + system's STREAM objects. * The Gray subclassable streams extension now works, thanks to a patch from Martin Atzmueller. * The full LOAD-FOREIGN extension (not just the primitive @@ -650,19 +674,43 @@ changes in sbcl-0.6.11 relative to sbcl-0.6.10: 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. -* fixed bug 40: TYPEP, SUBTYPEP, UPGRADED-ARRAY-ELEMENT-TYPE, - and UPGRADED-COMPLEX-PART-TYPE now work better with of compound - types built from undefined types, e.g. '(VECTOR SOME-UNDEF-TYPE). * 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. + +changes in sbcl-0.6.12 relative to sbcl-0.6.11: +* incompatible change: The old SB-EXT:OPTIMIZE-INTERFACE declaration + is no longer recognized. I apologize for this, because it was + listed in SB-EXT as a supported extension, but I found that + its existing behavior was poorly specified, as well as incorrectly + specified, and it looked like too much of a mess to straighten it + out. I have enough on my hands trying to get ANSI stuff to work.. +* many patches ported from CMU CL by Martin Atzmueller, with + half a dozen bug fixes in pretty-printing and the debugger, and + half a dozen others elsewhere +* fixed bug 13: Floating point infinities are now supported again. +* fixed bug 45a: Various internal functions required to support + complex special functions have been merged from CMU CL sources. + (When I was first setting up SBCL, I misunderstood a compile-time + conditional #-OLD-SPECFUN, and so accidentally deleted them.) +* The :SB-PROPAGATE-FLOAT-TYPE and :SB-PROPAGATE-FUN-TYPE features + are now supported, and enabled by default. Thus, the compiler can + handle many floating point and complex operations much less + inefficiently. (Thus e.g. you can implement a complex FFT + without consing!) +* improved support for type intersection and union, fixing bug 12 + (e.g., now (SUBTYPEP 'KEYWORD 'SYMBOL)=>T,T) and some other + more obscure bugs as well +* various fixes to make the cross-compiler more portable to + ANSI-conforming-but-different cross-compilation hosts (notably + Lispworks for Windows, following bug reports from Arthur Lemmens) +* a new workaround to make the cross-compiler portable to CMU CL + again despite its non-ANSI EVAL-WHEN, thanks to Martin Atzmueller +* new fasl file format version number (because of changes in byte + code opcodes and in internal representation of (OR ..) types) planned incompatible changes in 0.7.x: * The debugger prompt sequence now goes "5]", "5[2]", "5[3]", etc. @@ -673,4 +721,14 @@ planned incompatible changes in 0.7.x: * 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.) + matter, though, unless you are using profiling. If you never + profile anything, TRACE should continue to behave as before.) +* The fasl file extension may change, perhaps to ".fasl". +* The default output representation for unprintable ASCII characters + which, unlike e.g. #\Newline, don't have names defined in the + ANSI Common Lisp standard, may change to their ASCII symbolic + names: #\Nul, #\Soh, #\Stx, etc. +* INTERNAL-TIME-UNITS-PER-SECOND might increase, e.g. to 1000. +* MAYBE-INLINE will probably go away at some point, maybe 0.7.x, + maybe later, in favor of the ANSI-recommended idiom for making + a function optionally inline.