logo       
Google Custom Search
    AddThis Social Bookmark Button
-->

CVS: sbcl BUGS,1.153,1.154 version.lisp-expr,1.452,1.453: msg#00081

Subject: CVS: sbcl BUGS,1.153,1.154 version.lisp-expr,1.452,1.453
Update of /cvsroot/sbcl/sbcl
In directory usw-pr-cvs1:/tmp/cvs-serv22057

Modified Files:
        BUGS version.lisp-expr 
Log Message:
0.7.4.36:
        just BUGS entries



Index: BUGS
===================================================================
RCS file: /cvsroot/sbcl/sbcl/BUGS,v
retrieving revision 1.153
retrieving revision 1.154
diff -u -d -r1.153 -r1.154
--- BUGS        13 Jun 2002 00:47:51 -0000      1.153
+++ BUGS        16 Jun 2002 16:05:09 -0000      1.154
@@ -1290,6 +1290,62 @@
 179:
   (fixed in sbcl-0.7.4.28)
 
+180:
+  In sbcl-0.7.4.35, PCL seems not to understand the :MOST-SPECIFIC-LAST
+  option for PROGN method combination. It does understand that
+  :MOST-SPECIFIC-FIRST and :MOST-SPECIFIC-LAST belong with PROGN.
+  If I use another keyword, it complains:
+    (defgeneric foo ((x t))
+      (:method-combination progn :most-specific-first))
+  outputs
+    method combination error in CLOS dispatch:
+    Illegal options to a short method combination type.
+    The method combination type PROGN accepts one option which
+    must be either :MOST-SPECIFIC-FIRST or :MOST-SPECIFIC-LAST.
+  And when I use :MOST-SPECIFIC-FIRST, I get the expected default
+  behavior:
+    (defgeneric foo ((x t))
+      (:method-combination progn :most-specific-first))
+    (defmethod foo progn ((x number))
+      (print 'number))
+    (defmethod foo progn ((x fixnum))
+      (print 'fixnum))
+    (foo 14)
+  outputs
+    FIXNUM 
+    NUMBER 
+  and returns
+    NUMBER
+  But with :MOST-SPECIFIC-LAST,
+    (defgeneric foo ((x t))
+      (:method-combination progn :most-specific-last))
+    (defmethod foo progn ((x number))
+      (print 'number))
+    (defmethod foo progn ((x fixnum))
+      (print 'fixnum))
+    (foo 14)
+  the behavior doesn't change, giving output of
+    FIXNUM 
+    NUMBER 
+  and returning
+    NUMBER
+  Raymond Toy reported 2002-06-15 on sbcl-devel that CMU CL's PCL
+  doesn't seem to have this bug, outputting NUMBER before FIXNUM
+  as expected in the last case above.
+
+181:
+  Compiling 
+    (in-package :cl-user)
+    (defun bar (x)
+      (declare (type 0 x))
+      (cons x x))
+  signals 
+    bad thing to be a type specifier: 0
+  which seems fine, but also enters the debugger (instead of having
+  the compiler handle the error, convert it into a COMPILER-ERROR, and
+  continue compiling) which seems wrong.
+
+  
 DEFUNCT CATEGORIES OF BUGS
   IR1-#:
     These labels were used for bugs related to the old IR1 interpreter.

Index: version.lisp-expr
===================================================================
RCS file: /cvsroot/sbcl/sbcl/version.lisp-expr,v
retrieving revision 1.452
retrieving revision 1.453
diff -u -d -r1.452 -r1.453
--- version.lisp-expr   15 Jun 2002 03:19:15 -0000      1.452
+++ version.lisp-expr   16 Jun 2002 16:05:09 -0000      1.453
@@ -18,4 +18,4 @@
 ;;; for internal versions, especially for internal versions off the
 ;;; main CVS branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
 
-"0.7.4.35"
+"0.7.4.36"


_______________________________________________________________

Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/


<Prev in Thread] Current Thread [Next in Thread>