;;;; -*- coding: utf-8; -*-
changes in sbcl-1.0.22 relative to 1.0.21:
+ * minor incompatible change: LOAD-SHARED-OBJECT no longer by default looks
+ for the shared object in the current directory, but passes the native
+ namestring of the designated pathname to the operation system's shared
+ object loading function as-it.
* minor incompatible change: --disable-debugger toplevel option now takes
effect before processing of initialization files and --eval or --load
options.
Badichi)
* enhancement: :DONT-SAVE keyword argument has been added to
LOAD-SHARED-OBJECT for controlling interaction with
- SAVE-LISP-AND-DIE.
+ SAVE-LISP-AND-DIE, and UNLOAD-SHARED-OBJECT can be used to undo
+ the effects of an earlier LOAD-SHARED-OBJECT call.
* bug fix: ADJUST-ARRAY on multidimensional arrays used bogusly give
them a fill pointer unless :DISPLACED-TO or :INITIAL-CONTENTS were
provided. (reported by Cedric St-Jean)
* bug fix: COMPILE-FILE did not warn about undefined variable
references at toplevel, and LOAD of the resulting fasl did
not signal an error.
+ * bug fix: functions with non-required arguments used to end up with
+ (SB-C::&OPTIONAL-DISPATCH ...) as their name.
+ * bug fix: redefining a function with non-required arguments didn't
+ update the system's knowledge about its call signature properly.
+ * bug fix: fixed #431; incompatible alien record type redefinitions
+ are detected and handled. (reported by Neil Haven)
changes in sbcl-1.0.21 relative to 1.0.20:
* new feature: the compiler is able to track the effective type of a