* incompatible change: the SB-PCL package should now be considered a
private implementation detail, and no longer a semi-private MOP
interface.
+ * minor incompatible change: due to rearrangement for threads, the
+ control stack and binding stack are now allocated at arbitrary
+ addresses instead of being hardcoded per-port. Users affected by
+ this probably have to be doing advanced things with shared
+ libraries, and will know who they are.
* known functions, which cannot be open coded by backend, are
considered to be able to check types of their arguments.
(reported by Nathan J. Froyd)
* fixed a bug in computing method discriminating functions: it is
now possible to define methods specialized on classes which have
forward-referenced superclasses. (thanks to Gerd Moellmann)
- * fixed evaluation order in optional entries. (reported by Gilbert
+ * fixed evaluation order in optional entries. (reported by Gilbert
Baumann)
+ * SB-MOP:ENSURE-CLASS-USING-CLASS now takes its arguments in the
+ specified-by-AMOP order of (CLASS NAME &REST ARGS &KEY).
+ * fixed bug 20: DEFMETHOD can define methods using names that are
+ not the proper names of classes to designate class specializers.
+ * Experimental native threads support, on x86 Linux. This is not
+ compiled in by default: you need to add :SB-THREAD to the target
+ features. See the "Beyond ANSI" chapter of the manual for
+ details.
+ * sb-aclrepl module improvements: an integrated inspector, added
+ repl features, and a bug fix to :trace command.
* fixed some bugs revealed by Paul Dietz' test suite:
** COPY-ALIST now signals an error if its argument is a dotted
list;
+ ** condition slots are now accessed more correctly in the presence
+ of multiple initargs for a given slot;
+ ** the USE-VALUE, CONTINUE and STORE-VALUE functions now correctly
+ exclude restarts of the same name associated with a different
+ condition;
+ ** DEFCLASS of forward-referenced classes with another
+ forward-referenced class in the superclasses list no longer
+ causes an error;
-planned incompatible changes in 0.7.x:
+planned incompatible changes in 0.8.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
encapsulate functions, and it's not clear yet how e.g. UNPROFILE