common-lisp/sbcl.sbcl
1
0
Fork 0
mirror of git://git.code.sf.net/p/sbcl/sbcl synced 2026-09-10 07:26:40 -04:00
Code Issues Actions 8 Packages Projects Releases Wiki Activity

0.8.12.23: Signs of mellowing out in SBCL? Reversed NEWS file

Browse source 
to lastest-first order, and moved planned changes bit
           to TODO.
This commit is contained in:
Nikodemus Siivola 2004-07-05 16:27:47 +00:00
parent fdc38abbd1
commit 4009887b28
3 changed files with 2381 additions and 2381 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4743
NEWS
View file

File diff suppressed because it is too large Load diff

17
TODO
View file

@ -1,3 +1,20 @@
planned incompatible changes in 0.8.x:
* (not done yet, but planned:) When the profiling interface settles
down, 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.
for early 0.8.x:
* test file reworking

2
version.lisp-expr
View file

@ -17,4 +17,4 @@
;;; checkins which aren't released. (And occasionally for internal
;;; versions, especially for internal versions off the main CVS
;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
"0.8.12.22"
"0.8.12.23"