From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: heads up: goops class export
Date: Tue, 03 May 2011 15:11:00 +0200 [thread overview]
Message-ID: <m362psrkt7.fsf@unquote.localdomain> (raw)
In-Reply-To: <87sjswnfhc.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 03 May 2011 14:19:43 +0200")
Hi :)
On Tue 03 May 2011 14:19, ludo@gnu.org (Ludovic Courtès) writes:
> Andy Wingo <wingo@pobox.com> writes:
>
>> smob-name->class
>
> Yes, why not. (It’s equivalent to (@@ (oop goops) foobar) in terms of
> providing access to everyone, though.)
OK. GOOPS really isn't for the ocap folks, given
class-direct-subclasses, the cross-module implications of defining a new
method on a generic, etc :)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-05-03 13:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-01 20:32 heads up: goops class export Andy Wingo
2011-05-03 8:50 ` Ludovic Courtès
2011-05-03 9:31 ` Andy Wingo
2011-05-03 12:19 ` Ludovic Courtès
2011-05-03 13:11 ` Andy Wingo [this message]
2011-07-01 10:03 ` 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=m362psrkt7.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).