From: <dsmich@roadrunner.com>
To: David Pirotte <david@altosw.be>, Andy Wingo <wingo@pobox.com>
Cc: 20423@debbugs.gnu.org
Subject: bug#20423: goops - inheritance of slot options
Date: Thu, 23 Jun 2016 21:06:36 -0400 [thread overview]
Message-ID: <20160624010636.CPEPG.255078.root@cdptpa-web03> (raw)
In-Reply-To: <20160623200857.1e0d3e51@capac>
---- David Pirotte <david@altosw.be> 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
next prev parent reply other threads:[~2016-06-24 1:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 2:05 bug#20423: goops - inheritance of slot options David Pirotte
2016-06-23 20:23 ` Andy Wingo
2016-06-23 23:08 ` David Pirotte
2016-06-24 1:06 ` dsmich [this message]
2016-06-24 5:04 ` Andy Wingo
2016-07-12 20:02 ` David Pirotte
2016-06-24 5:12 ` Andy Wingo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160624010636.CPEPG.255078.root@cdptpa-web03 \
--to=dsmich@roadrunner.com \
--cc=20423@debbugs.gnu.org \
--cc=david@altosw.be \
--cc=wingo@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).