+planned incompatible changes in 0.8.x:
+ * (not done yet, but planned:) 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. If you never profile anything, TRACE should continue to
+ behave as before.)
+ * (not done yet, but planned:) Inlining can now be controlled the
+ ANSI way, without MAYBE-INLINE, since the idiom
+ (DECLAIM (INLINE FOO))
+ (DEFUN FOO (..) ..)
+ (DECLAIM (NOTINLINE FOO))
+ (DEFUN BAR (..) (FOO ..))
+ (DEFUN BLETCH (..) (DECLARE (INLINE FOO)) (FOO ..))
+ now does what ANSI says it should. The CMU-CL-style
+ SB-EXT:MAYBE-INLINE declaration is now deprecated and ignored.
+
for early 0.8.x:
* test file reworking
- ** non-x86 ports now pass irrat.pure.lisp
** ports with less than 256Mb of heap (sparc, ppc and mips)
now don't fail bit-vector.impure-cload.lisp
* faster bootstrapping (both make.sh and slam.sh)
* Some work on conditions emitted by the system
** eliminated COMPILER-WARN and COMPILER-STYLE-WARN, which
were simply limited versions of WARN and STYLE-WARN.
+ ** made STYLE-WARN parallel WARN more closely (by accepting
+ a condition type, which should be a subtype of
+ STYLE-WARNING, and initargs, as well as a format
+ string and format arguments for SIMPLE-STYLE-WARNING.
+ (WARN can also be used to signal STYLE-WARNINGs, but
+ STYLE-WARN helps to document the code)
** eliminated use of INHIBIT-WARNINGS by code emitted by the
system from user code.
** caused use of INHIBIT-WARNINGS to signal a STYLE-WARNING.