From: Andy Wingo <wingo@pobox.com>
To: Krister Svanlund <krister.svanlund@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Making every goops object applicable
Date: Tue, 15 May 2012 20:36:58 +0200 [thread overview]
Message-ID: <87sjf1mgtx.fsf@pobox.com> (raw)
In-Reply-To: <CAO_vGe_q36h7z3zs_GuVKgNqk5g0RN_e1ViFEswVG3j7OuLozQ@mail.gmail.com> (Krister Svanlund's message of "Mon, 14 May 2012 19:24:41 +0200")
Hi Krister,
On Mon 14 May 2012 19:24, Krister Svanlund <krister.svanlund@gmail.com> writes:
> In our work to look into how Python 3 could be implemented for Guile
> we have figured out that the only way to make a goops object
> applicable is to have it inherit <applicable-struct>. This does not
> always work the way it could be expected, for example when inheriting
> from several classes.
It should work. It doesn't, as you have found. The reason is that the
meta-object protocol for generic functions was never completely
implemented. When/if someone implements it, the result will be objects
that do have that magical applicable flag set.
Regards,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2012-05-15 18:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 17:24 Making every goops object applicable Krister Svanlund
2012-05-14 22:16 ` Mark H Weaver
[not found] ` <CAO_vGe-fjX4iHusc5FdLV89i6+eBt3iCF4KP_S43LbP2ZQu4UA@mail.gmail.com>
2012-05-15 0:46 ` Fwd: " Krister Svanlund
2012-05-15 15:46 ` Mark H Weaver
2012-05-15 19:43 ` Neil Jerram
2012-05-16 5:18 ` Mark H Weaver
2012-05-15 12:31 ` Ludovic Courtès
2012-05-15 18:36 ` Andy Wingo [this message]
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=87sjf1mgtx.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=krister.svanlund@gmail.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).