From: William Harold Newman <william.newman@ai...> - 2005-01-26 02:48:49
I finished putting sbcl-0.8.19 tarballs up on the project file release
page perhaps half an hour ago; party on.
from the NEWS file:
changes in sbcl-0.8.19 relative to sbcl-0.8.18:
* new port: SBCL now works in native 64-bit mode on x86-64/Linux
platform. The port supports 61-bit fixnums, large memory spaces
and reloading shared object files.
* enhancement: saving cores with foreign code loaded is now
supported on ppc/Darwin in addition to the previously supported
* enhancement: the statistical profiler now walks deeper into the
call stack for more meaningful call-graphs and accrued time
reports (x86/x86-64 only). It also now reports time spent in
* enhancement: it is now possible to trace most individual methods
of a generic function in addition to tracing the generic function
* bug fix: invalid :DEFAULT-INITARGS are detected in compiled calls
* bug fix: defaulted initargs are passed to INITIALIZE-INSTANCE and
SHARED-INITIALIZE methods from compiled calls to MAKE-INSTANCE.
* bug fix: COERCE to (COMPLEX FLOAT) of a complex number no longer
produces an error. (thanks to Vincent Arkesteijn)
* bug fix: NAMESTRING on pathnames with :WILD components in their
directories works correctly. (thanks to Artem V. Andreev)
* fixed bug 125: compiler preserves identity of closures. (reported
by Gabe Garza)
* bug fixed: functions with &REST arguments sometimes failed with
"Undefined function" when compiled with (DEBUG 3). (reported by
Robert J. Macomber)
* bug fix: overflow during compiling of setting element of a bit
vector with constant index and value. (reported by Timmy Douglas)
* build fix: fixed the dependence on *LOAD-PATHNAME* and
*COMPILE-FILE-PATHNAME* being absolute pathnames.
* on x86 compiler partially supports stack allocation of dynamic-extent
* GO and RETURN-FROM do not check the extent of their exit points
when compiled with SAFETY 0.
* fixed some bugs related to Unicode integration:
** encoding and decoding errors are now much more robustly
handled; it should now be possible to recover even from invalid
input or output to the terminal. (thanks to Teemu Kalvas)
** provided a first cut at implementing STRING-TO-OCTETS and
OCTETS-TO-STRING. (thanks to Robert J. Macomber)
** altered the SB-MD5 contributed module slightly, changing the
interface just enough for it to be supportable for builds where
lisp characters are not eight bits.
* fixed some bugs revealed by Paul Dietz' test suite:
** the FORMATTER-generated functions for ~V[ conditionals require
the correct number of arguments.
** READ-FROM-STRING returns the mandated second value when applied
to displaced strings.
** the #\Rubout and #\Backspace characters are treated as invalid
constituent characters by the tokenizer.
William Harold Newman <william.newman@...>
"We reject Kings, presidents, and voting.
We believe in rough consensus and running code."
-- Dave Clark (IETF), 1992