encapsulation also seems closer to the spirit of the ANSI
specification.)
+changes in sbcl-0.7.3 relative to sbcl-0.7.2:
+ * SBCL now runs on the PPC archtiecture under Linux. It actually did
+ this as of 0.7.1.45, but was left out of the previous news section
+ (thanks to Dan Barlow)
+ * SBCL now runs on the Solaris operating system on SPARC architectures
+ (thanks to Christophe Rhodes's port of the CMUCL runtime)
+ * cleanups to the runtime on SPARC, both Linux and Solaris, and for
+ gcc>=3 (thanks to Nathan Froyd and Ingvar Mattsson)
+ * SPARC backend cleanups, allowing builds of cores optimized for V8
+ and V9 SPARCS, and also emission of code targeted to a particular
+ backend chosen at runtime (thanks to Christophe Rhodes and Raymond
+ Toy)
+ * ANSI's DEFINE-SYMBOL-MACRO is now supported. (thanks to Nathan
+ Froyd porting CMU CL code originally by Douglas Thomas Crosher)
+ * The fasl file format has changed again, to allow the compiler's
+ INFO database to support symbol macros.
+ * The user manual (in doc/) is formatted into HTML more nicely.
+ (thanks to coreythomas)
+ * The system is smarter about SUBTYPEP relationships, especially
+ those involving NOT types (including types such as ATOM which are
+ represented internally using NOT types). Thus SUBTYPEP is less
+ likely to return (VALUES NIL NIL) in general, and in particular
+ bugs 58 and (the remaining bits of) bug 50 are fixed. (thanks to
+ Christophe Rhodes)
+ * The fasl file format has changed again, because the internal
+ representation of types now includes a new slot to support the new
+ SUBTYPEP-of-NOT-types logic.
+ * (not a change in the main branch of SBCL, but a related prototype
+ which can hopefully be merged into the main branch of SBCL in the
+ future:) Brian Spilsbury has produced a Unicode-enabled variant of
+ sbcl-0.7.0, available as a patch against sbcl-0.7.0 at
+ <http://designix.com.au/brian/SBCL/sbcl-0.7.0-unicode.p0.gz>.
+ * Bugfix to GET-DISPATCH-MACRO-CHAR, now returning NIL for undefined
+ dispatch macro character combinations (thanks to Alexey Dejenka)
+
planned incompatible changes in 0.7.x:
* When the profiling interface settles down, maybe in 0.7.x, maybe
later, it might impact TRACE. They both encapsulate functions, and