From 57328db4dfb8d90a017207f00a1af4264ff82dbf Mon Sep 17 00:00:00 2001 From: William Harold Newman Date: Wed, 27 Nov 2002 14:47:09 +0000 Subject: [PATCH] 0.7.10: release, tagged as sbcl_0_7_10 --- CREDITS | 3 +++ NEWS | 27 +++++++++++++++++---------- src/code/early-fasl.lisp | 6 +++++- version.lisp-expr | 2 +- 4 files changed, 26 insertions(+), 12 deletions(-) diff --git a/CREDITS b/CREDITS index 7b8096b..d0de362 100644 --- a/CREDITS +++ b/CREDITS @@ -615,6 +615,9 @@ Peter Van Eynde: of bug reports resulting from that, and submitted many other bug reports as well. +Valtteri Vuorikoski: + He ported SBCL to NetBSD. + Colin Walters: His O(N) implementation of the general case of MAP, posted on the cmucl-imp@cons.org mailing list, was the inspiration for similar MAP diff --git a/NEWS b/NEWS index 8b7bae7..5a97db5 100644 --- a/NEWS +++ b/NEWS @@ -1424,20 +1424,27 @@ changes in sbcl-0.7.10 relative to sbcl-0.7.9: * fixed bug 194: error messages are now more informative when there is no primary method applicable in a call to a generic function. (thanks to Gerd Moellmann) + * fixed bug in command line argument checking (thanks to Julian + Fondren) + * fixed bug in COUNT-IF, making it handle :FROM-END correctly + (thanks to Matthew Danish) + * incremented fasl file version number, because of the + SXHASH-related changes in the layout of CLOS data structures 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 - it's not clear yet how e.g. UNPROFILE will interact with TRACE - and UNTRACE. (This shouldn't matter, though, unless you are - using profiling. If you never profile anything, TRACE should - continue to behave as before.) -* Inlining can now be controlled the ANSI way, without - MAYBE-INLINE, since the idiom + * (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 + will interact with TRACE + and UNTRACE. (This shouldn't matter, though, unless you are + using profiling. If you never profile anything, TRACE should + continue to behave as before.) + * (not done yet, but planned:) Inlining can now be controlled the + ANSI way, without MAYBE-INLINE, since the idiom (DECLAIM (INLINE FOO)) (DEFUN FOO (..) ..) (DECLAIM (NOTINLINE FOO)) (DEFUN BAR (..) (FOO ..)) (DEFUN BLETCH (..) (DECLARE (INLINE FOO)) (FOO ..)) - now does what ANSI says it should. The CMU-CL-style - SB-EXT:MAYBE-INLINE declaration is now deprecated and ignored. + now does what ANSI says it should. The CMU-CL-style + SB-EXT:MAYBE-INLINE declaration is now deprecated and ignored. diff --git a/src/code/early-fasl.lisp b/src/code/early-fasl.lisp index c3c7046..cc74cc2 100644 --- a/src/code/early-fasl.lisp +++ b/src/code/early-fasl.lisp @@ -42,7 +42,7 @@ ;;; versions which break binary compatibility. But it certainly should ;;; be incremented for release versions which break binary ;;; compatibility. -(def!constant +fasl-file-version+ 34) +(def!constant +fasl-file-version+ 35) ;;; (record of versions before 0.7.0 deleted in 0.7.1.41) ;;; 23 = sbcl-0.7.0.1 deleted no-longer-used EVAL-STACK stuff, ;;; causing changes in *STATIC-SYMBOLS*. @@ -67,6 +67,10 @@ ;;; causing old utility functions like COERCE-TO-SIMPLE-VECTOR to go away ;;; 34: (2002-10-05) changed implementation of DEFMACRO, so %%DEFMACRO ;;; was deleted +;;; 35: (2002-11-27) (incremented version before 0.7.10 release, +;;; reflecting changes from a week or more ago) changed layout of +;;; CLOS objects to support SXHASH returning values other than 42 +;;; for STANDARD-OBJECT ;;; the conventional file extension for our fasl files (declaim (type simple-string *fasl-file-type*)) diff --git a/version.lisp-expr b/version.lisp-expr index 5fd1124..773ac9d 100644 --- a/version.lisp-expr +++ b/version.lisp-expr @@ -18,4 +18,4 @@ ;;; versions, especially for internal versions off the main CVS ;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".) -"0.7.9.68" +"0.7.10" -- 1.7.10.4