0.7.4.36:

[sbcl.git] / BUGS

diff --git a/BUGS b/BUGS
index 4573bce..eb00513 100644 (file)
--- a/BUGS
+++ b/BUGS
@@ -972,18 +972,6 @@ WORKAROUND:
       (let ((x (1+ x)))
         (call-next-method)))
   Now (FOO 3) should return 3, but instead it returns 4.
-    
-137:
-  (SB-DEBUG:BACKTRACE) output should start with something
-  including the name BACKTRACE, not (as in 0.pre7.88)
-  just "0: (\"hairy arg processor\" ...)". Until about
-  sbcl-0.pre7.109, the names in BACKTRACE were all screwed
-  up compared to the nice useful names in sbcl-0.6.13.
-  Around sbcl-0.pre7.109, they were mostly fixed by using
-  NAMED-LAMBDA to implement DEFUN. However, there are still
-  some screwups left, e.g. as of sbcl-0.pre7.109, there are
-  still some functions named "hairy arg processor" and
-  "SB-INT:&MORE processor".
 
 141: 
   Pretty-printing nested backquotes doesn't work right, as 
@@ -1288,9 +1276,6 @@ WORKAROUND:
     (defclass c0 (b) ())
     (make-instance 'c19)
 
-177:
-  (fixed in sbcl-0.7.4.24)
-
 178: "AVER failure compiling confused THEs in FUNCALL"
   In sbcl-0.7.4.24, compiling
     (defun bug178 (x)
@@ -1303,13 +1288,64 @@ WORKAROUND:
       (funcall (the nil x)))
 
 179:
-  Reported by Miles Egan on sbcl-devel 11 June 2002:
-  In sbcl-0.7.4.x, doing
-    $ touch /tmp/bad\*
-    $ sbcl
-    * (directory "/tmp/*")
-  yields an error: "bad place for a wild pathname"
+  (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.