0.7.0.8:

	added DB's bug 133 test case

diff --git a/NEWS b/NEWS
index 2cef80c..411186e 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -981,19 +981,28 @@ changes in sbcl-0.7.0 relative to sbcl-0.6.13:
   some of which are apparent above.
 
 changes in sbcl-0.7.1 relative to sbcl-0.7.0:
-* SB-ALIEN:LOAD-FOREIGN and SB-ALIEN:LOAD-1-FOREIGN are set
-  up properly again. (There was a packaging bug in 0.7.0 which
-  left their definitions in SB-SYS::LOAD-FOREIGN and 
-  SB-SYS::LOAD-1-FOREIGN.)
-* DEFGENERIC is now choosier about the methods it redefines, so that
-  reLOADing a previously-LOADed file containing DEFGENERICs does
-  the right thing now. Thus, the Lispy edit/reLOAD-a-little/test
-  cycle now works as it should. (thanks to Alexey Dejneka)
-* Bug 106 (types (COMPLEX FOO) where FOO is an obscure type) was
-  fixed by Christophe Rhodes. (He actually submitted this patch
-  months ago, and I delayed until after 0.7.0.)
-* Bug 111 (internal compiler confusion about runtime checks on
-  FUNCTION types) was fixed by Alexey Dejneka.
+* mostly bug fixes:
+  ** SB-ALIEN:LOAD-FOREIGN and SB-ALIEN:LOAD-1-FOREIGN are set
+     up properly again. (There was a packaging bug in 0.7.0 which
+     left their definitions in SB-SYS::LOAD-FOREIGN and 
+     SB-SYS::LOAD-1-FOREIGN. LOAD-FOREIGN and LOAD-1-FOREIGN are
+     vital for most things which interface to C-level interfaces,
+     like extensions working with sockets or databases or
+     Perl-compatible regexes or whatever, and the need to fix
+     this bug is the main reason that 0.7.1 was released so
+     soon after 0.7.0.)
+  ** DEFGENERIC is now choosier about the methods it redefines, so that
+     reLOADing a previously-LOADed file containing DEFGENERICs does
+     the right thing now. Thus, the Lispy edit/reLOAD-a-little/test
+     cycle now works as it should. (thanks to Alexey Dejneka)
+  ** Bug 106 (types (COMPLEX FOO) where FOO is an obscure type) was
+     fixed by Christophe Rhodes. (He actually submitted this patch
+     months ago, and I delayed until after 0.7.0.)
+  ** Bug 111 (internal compiler confusion about runtime checks on
+     FUNCTION types) was fixed by Alexey Dejneka.
+* Some internal cleanups (getting rid of variables which aren't
+  needed now that the byte interpreter is gone) caused the fasl
+  file format number to change again.
 
 planned incompatible changes in 0.7.x:
 * When the profiling interface settles down, maybe in 0.7.x, maybe

diff --git a/tests/alien.impure.lisp b/tests/alien.impure.lisp
index d5d0423..8638d5c 100644 (file)
--- a/tests/alien.impure.lisp
+++ b/tests/alien.impure.lisp
@@ -23,5 +23,10 @@
 (setf (sb-alien:extern-alien "current_control_stack_pointer" sb-alien:unsigned)
       (sb-alien:extern-alien "current_control_stack_pointer" sb-alien:unsigned))
 
+;;; bug 133, fixed in 0.7.0.5: Somewhere in 0.pre7.*, C void returns
+;;; were broken ("unable to use values types here") when
+;;; auto-PROCLAIM-of-return-value was added to DEFINE-ALIEN_ROUTINE.
+(sb-alien:define-alien-routine ("free" free) void (ptr (* t) :in))
+
 ;;; success
 (quit :unix-status 104)