#233: Evaluation of (DIRECTORY "/*/") fails
------------------------+---------------------------------------------------
Reporter: ehuelsmann | Owner: mevenson
Type: defect | Status: new
Priority: major | Milestone:
Component: libraries | Version: 1.1.0-dev
Keywords: |
------------------------+---------------------------------------------------
Reported by Stas Boukarev on #abcl:
(DIRECTORY "/*/")
--->
#<THREAD "interpreter" {E2B9E5}>: Debugger invoked on condition of type
TYPE-ERR
OR
The value NIL is not of type (OR PATHNAME STRING FILE-STREAM SYSTEM:JAR-
STREAM
SYSTEM:URL-STREAM).
Restarts:
0: TOP-LEVEL Return to top level.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/233>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#239: defgeneric with unsuitable :generic-function-class gives incomprehensible
error
-----------------------+----------------------------------------------------
Reporter: rschlatte | Owner: ehuelsmann
Type: defect | Status: new
Priority: minor | Milestone:
Component: (A)MOP | Version:
Keywords: |
-----------------------+----------------------------------------------------
Compiling and loading the following (incorrect) file gives an error saying
that foo-generic-function is not of type standard-generic-function. The
real error is that foo-generic-function must be defined with (:metaclass
funcallable-standard-class) to be suitable as a generic function class.
{{{
(require :clos)
(defclass foo-generic-function (standard-generic-function))
(defgeneric goo (a b)
(:generic-function-class foo-generic-function)
(:method (a b)
(princ "default method")))
(print #'goo)
}}}
The attached patch would emit a full warning in defgeneric, but currently
find-class does not implement correct behavior when called with 3
parameters.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/239>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#242: Unused &key warnings in defmethod forms should not cause style-warnings
-----------------------+----------------------------------------------------
Reporter: rschlatte | Owner: ehuelsmann
Type: defect | Status: new
Priority: minor | Milestone:
Component: compiler | Version:
Keywords: |
-----------------------+----------------------------------------------------
CLHS 7.6.5 says: "The lambda list congruence rules require that each
method accept all of the keyword arguments mentioned after &key in the
generic function definition, by accepting them explicitly, by specifying
&allow-other-keys, or by specifying &rest but not &key."
Currently, when compiling a file containing the form
{{{(defmethod foo ((x fixnum) &key y z) x)}}}
we get style warnings about unused variables y and z. I think that these
style warnings can be safely elided, since a typo in the arglist will lead
to another style warning "Undefined variable A assumed special".
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/242>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#231: DEFSTRUCT accessor functions overwrite accessors in :INCLUDEd structs
------------------------+---------------------------------------------------
Reporter: ehuelsmann | Owner: mevenson
Type: defect | Status: new
Priority: major | Milestone: 1.1.0
Component: libraries | Version:
Keywords: |
------------------------+---------------------------------------------------
Ralf Moeller reports:
The following file causes a problem in ABCL (1.1.0-dev-svn-14041) when
compiled (!) and loaded.
(in-package cl-user)
(defstruct a (s1 nil))
(defstruct (b (:include a) (:conc-name foo-)) (s2 nil))
(defstruct (c (:include a) (:conc-name foo-)) (s3 nil))
(defun test ()
(let ((x (make-b :s1 1 :s2 2)))
(foo-s1 x)))
CL-USER(4): (test)
#<THREAD "interpreter" {2EF7D41F}>: Debugger invoked on condition of type
SIMPLE-TYPE-ERROR
The value #<B {564434F7}> is not of type C.
Restarts:
0: TOP-LEVEL Return to top level.
[1] CL-USER(6): (lisp-implementation-version)
"1.1.0-dev-svn-14041"
[1] CL-USER(7):
The problem is that the defstruct declaration for c "overwrites" the
accessor foo-s1 generated by defstruct b.
If foo-s1 is called for a b instance, the type assertions introduced by
define-reader (and define-writer, see the
ABCL implementation for defstruct) cause the error described above.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/231>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#165: pprint-logical-block fails for format with list directive
----------------------------+-----------------------------------------------
Reporter: mevenson | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone: 0.27
Component: other | Version: 0.27
Keywords: sbcl-buildhost |
----------------------------+-----------------------------------------------
Derived from the problems getting SBCL to compile, the following test
fails with complaints in the XP package:
{{{
(defparameter *stream* *error-output*)
(defun pprint-test ()
(pprint-logical-block (*stream* nil :prefix "---")
(format *stream* "~(~A~)" '(1 2 3 4))))
}}}
with this error
{{{
The value #S(XP::XP-STRUCTURE :BASE-STREAM #S(SLIME-OUTPUT-STREAM) :LINE-
LENGTH 70 :LINE-LIMIT NIL :LINE-NO 1 :DEPTH-IN-BLOCKS 2 :BLOCK-STACK #(0 0
3 NIL NIL NIL NIL NIL NIL NIL ...) :BLOCK-STACK-PTR 2 :BUFFER … is not of
type STREAM.
[Condition of type TYPE-ERROR]
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/165>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#118: Lisp.getUpgradedElementType returns more types than supported by
'make_array.java'
------------------------+---------------------------------------------------
Reporter: ehuelsmann | Owner: nobody
Type: defect | Status: new
Priority: major | Milestone:
Component: libraries | Version:
Keywords: |
------------------------+---------------------------------------------------
The above leads to possible failure: each upgraded element type has its
own associated defaultInitialValue. If the code does not specify the right
initial value, NIL is taken, which probably is not a good fit.
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/118>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
#271: ASDF-2.26 changes synced upstream
-------------------------------------+--------------------------------------
Reporter: mevenson | Owner: somebody
Type: defect | Status: new
Priority: major | Milestone: 1.1.0
Component: other | Version: 1.1.0-dev
Keywords: quicklisp asdf upstream |
-------------------------------------+--------------------------------------
ABCL relies on #+abcl conditional changes that need to be synced upstream.
The Quicklisp November 2012 Client is providing stock ASDF-2.26, and I'm
not sure who is currently "winning".
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/271>
armedbear <http://common-lisp.net/project/armedbear>
armedbear