[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#20423: goops - inheritance of slot options
From: |
dsmich |
Subject: |
bug#20423: goops - inheritance of slot options |
Date: |
Thu, 23 Jun 2016 21:06:36 -0400 |
---- David Pirotte <address@hidden> wrote:
> Hi Andy,
>
> > For what it's worth this is a part of GOOPS's design AFAIU: all slot
> > definitions are unique. Two slots named S declared on classes A and B
> > are distinct, even if A is a superclass of B.
>
> Well, as I explained in the original report, the only specification we have
> is CLOS:
> Stklos, upon which Guile GOOPS is based, clearly state in its manual, among
> the
> first paragraphs, that it implements the CLOS protocol [a subset]: there is no
> 'redesign' anywhere in Stlkos [it just lacks :before and :after methods
> AFAICT].
>
> AFAICT, there is no Guile 'official' document stating clearly, neither in the
> manual, that GOOPS authors decided to redesign this part of the protocol and
> why...
> is there?
Way way back, goops was a separate project from guile. This TODO file has
some info on where Mikael was planning on going with it:
http://cvs.savannah.gnu.org/viewvc/guile/guile-oops/TODO?revision=1.19&root=guile&view=markup
-Dale