Opened 16 years ago
Closed 15 years ago
#38 closed defect (fixed)
CLOS :metaclass support
Reported by: | ehuelsmann | Owned by: | ehuelsmann |
---|---|---|---|
Priority: | major | Milestone: | 0.20 |
Component: | other | Version: | |
Keywords: | Cc: | ||
Parent Tickets: |
Description (last modified by )
Blake McBride? reports:
Running the code:
(defclass meta-class1 (standard-class) (cv1 cv2 cv3) (:metaclass standard-class)) (defclass class1 (standard-object) (iv1 iv2 iv3) (:metaclass meta-class1))
The second object returns:
#<STANDARD-CLASS CLASS1 {F673CC}>
It should be:
#<META-CLASS1 CLASS1 {F673CC}>
Not only is it reporting the wrong class of class1 but it doesn't work either. I suppose ABCL doesn't support the :metaclass option. It just ignores it. The problem is that without that option ABCL's CLOS is severely limited. Any plans to fix this?
Thanks.
Blake McBride?
Change History (10)
comment:1 Changed 15 years ago by
Milestone: | → 0.20 |
---|---|
Owner: | changed from somebody to ehuelsmann |
Status: | new → accepted |
comment:2 Changed 15 years ago by
comment:3 Changed 15 years ago by
Description: | modified (diff) |
---|
comment:4 Changed 15 years ago by
comment:5 Changed 15 years ago by
comment:6 Changed 15 years ago by
(In [12534]) Make sure non-standard (meta) classes aren't cast to LispClass?
as they are StandardObject?-s.
Re #38.
comment:9 Changed 15 years ago by
comment:10 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
Note: See
TracTickets for help on using
tickets.
(In [12527]) Make all class accessor functions generic functions instead
Because classes may be of a different Java type than
See #38.