[armedbear-ticket] [armedbear] #38: CLOS :metaclass support
armedbear
armedbear-devel at common-lisp.net
Sat Mar 13 21:45:54 UTC 2010
#38: CLOS :metaclass support
-------------------------+--------------------------------------------------
Reporter: ehuelsmann | Owner: ehuelsmann
Type: defect | Status: accepted
Priority: major | Milestone: 0.20
Component: other | Version:
Resolution: | Keywords:
-------------------------+--------------------------------------------------
Description changed by ehuelsmann:
Old description:
> 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
New description:
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
--
--
Ticket URL: <http://trac.common-lisp.net/armedbear/ticket/38#comment:3>
armedbear <http://common-lisp.net/project/armedbear>
armedbear
More information about the armedbear-ticket
mailing list