From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: goops proposal: proper struct classes
Date: Thu, 05 May 2011 22:39:06 +0200 [thread overview]
Message-ID: <m34o58x4ph.fsf@unquote.localdomain> (raw)
In-Reply-To: <8739ksnbnf.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 05 May 2011 22:19:16 +0200")
On Thu 05 May 2011 22:19, ludo@gnu.org (Ludovic Courtès) writes:
>> Vtables *are* classes, on a fundamental level. Bare vtables are not as
>> nice as <class>, but they do describe instances. SCM_CLASS_OF() is
>> SCM_STRUCT_VTABLE().
>
> OK, it would be more elegant.
>
> Can it be achieved without GOOPsifying too much the rest of Guile?
> I mean, creating and accessing raw structs should remain as lightweight as
> currently, so that syntactic-only records à la SRFI-9 can be
> implemented. GOOPS objects are currently heavyweight compared to raw
> structs.
Yes, I think it can. Actually the motivation was to remove the call to
scm_i_define_class_for_vtable from structs, which will allow proper
layering of goops and structs. (You are right to be concerned, I think;
GOOPS is pretty neat to have, and appropriate to some domains, but has
fundamental problems with modularity.)
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-05-05 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-01 20:19 goops proposal: proper struct classes Andy Wingo
2011-05-05 16:35 ` Ludovic Courtès
2011-05-05 18:25 ` Andy Wingo
2011-05-05 20:19 ` Ludovic Courtès
2011-05-05 20:39 ` Andy Wingo [this message]
2011-11-22 22:23 ` 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=m34o58x4ph.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).