not cause a type error;
** CONSTANTP now returns true for all self-evaluating objects.
+changes in sbcl-0.7.13 relative to sbcl-0.7.12:
+ * fixed a bug in LOG, so that LOG of a rational argument near 1 now
+ gives a closer approximation to the right answer than previously.
+ (thanks to Raymond Toy)
+ * fixed bug 157: TYPEP, SUBTYPEP, UPGRADED-ARRAY-ELEMENT-TYPE and
+ UPGRADED-COMPLEX-PART-TYPE now take (ignored, in all situations)
+ optional environment arguments, as required by ANSI.
+ * fixed bugs in other functions taking environment objects, allowing
+ calls with an explicit NIL environment argument to be compiled
+ without error.
+ * fixed bug 228: primary return values from
+ FUNCTION-LAMBDA-EXPRESSION are either NIL or suitable for input to
+ COMPILE or FUNCTION.
+ * fixed a bug in DEFSTRUCT: predicates for :NAMED structures with
+ :TYPE will no longer signal errors on innocuous objects.
+ * fixed bug 231b: SETQ is better at respecting type declarations in
+ the lexical environment.
+ * fixed a bug in DEFCLASS: classes named by symbols with no or
+ unprintable packages can now be defined.
+ * fixed a bug in RESTART-BIND: The :TEST-FUNCTION option had been
+ carelessly renamed to :TEST-FUN. (thanks to Robert E. Brown)
+ * fixed compiler failure related to checking types of functions.
+ (reported by Robert E. Brown)
+ * the compiler is now much more consistent in its error-checking
+ treatment of bounding index arguments to sequence functions: in
+ (SAFETY 3) code, errors will be signalled in almost all cases if
+ invalid sequence bounding indices are passed to functions defined
+ by ANSI to operate on sequences.
+ * fixed some bugs revealed by Paul Dietz' test suite:
+ ** ARRAY-IN-BOUNDS-P now allows arbitrary integers as arguments,
+ not just nonnegative fixnums;
+ ** the logical bit-array operators such as BIT-AND now accept an
+ explicit NIL for their "opt-arg" argument (to indicate a
+ freshly-consed result bit-array);
+
planned incompatible changes in 0.7.x:
* (not done yet, but planned:) When the profiling interface settles
down, maybe in 0.7.x, maybe later, it might impact TRACE. They both