From: Neil Jerram <neil@ossau.uklinux.net>
Cc: Guile Users <guile-user@gnu.org>, guile-devel@gnu.org
Subject: Re: GOOPS-based SRFI-35 implementation
Date: 10 Mar 2004 09:17:19 +0000 [thread overview]
Message-ID: <85fzchdpsw.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87r7w3yuem.fsf@ivanova.rotty.yi.org>
Andreas Rottmann <a.rottmann@gmx.at> writes:
> Neil Jerram <neil@ossau.uklinux.net> writes:
>
> > (make-compound-condition &i/o-condition (...)
> > &runtime-condition (...))
> >
> I think you mean condition instead of make-compound-condition here.
Yes, you're right.
> It may be, but this probably involves "caching" defined (via
> define-class or the condition macro) condition types by their
> supertypes. This, in turn, disallows defining different define-class
> statements specifiying the same supers (if the supers are conditions).
Good point.
> Another, much more serious problem is the following: [...]
Yes, I see. OK, I'm convinced by your arguments.
On rereading, I see that SRFI-35's condition types follow a single
inheritance hierarchy, and that compound conditions are a way of
combining different types within the hierarchy. This is quite
different from the multiple inheritance allowed by GOOPS. I'd now say
that it remains to be seen whether it will be useful and workable to
combine GOOPS-defined multiple inheritance conditions with those that
can be defined by SRFI-35.
Regards,
Neil
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-03-10 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-28 15:53 GOOPS-based SRFI-35 implementation Andreas Rottmann
2004-03-03 16:02 ` Neil Jerram
2004-03-04 0:20 ` Andreas Rottmann
2004-03-06 12:05 ` Neil Jerram
2004-03-06 14:52 ` Andreas Rottmann
2004-03-08 20:07 ` Andreas Rottmann
2004-03-10 9:17 ` Neil Jerram [this message]
2004-03-11 15:38 ` Mikael Djurfeldt
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=85fzchdpsw.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
/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).