From: Krister Svanlund <krister.svanlund@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Making every goops object applicable
Date: Mon, 14 May 2012 19:24:41 +0200 [thread overview]
Message-ID: <CAO_vGe_q36h7z3zs_GuVKgNqk5g0RN_e1ViFEswVG3j7OuLozQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]
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.
Apparently this works by some flag being set by <applicable-strukt> in
libguile for the object and that flag is checked during application,
calling the 'procedure slot if it's set with some optimization assuming
that 'procedure is the first slot.
Is this correct and if so, is there any particular reasoning behind this
rather than just having all classes that has the slot 'procedure be
applicable?
Yours,
Krister Svanlund
[-- Attachment #2: Type: text/html, Size: 762 bytes --]
next reply other threads:[~2012-05-14 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 17:24 Krister Svanlund [this message]
2012-05-14 22:16 ` Making every goops object applicable 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
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=CAO_vGe_q36h7z3zs_GuVKgNqk5g0RN_e1ViFEswVG3j7OuLozQ@mail.gmail.com \
--to=krister.svanlund@gmail.com \
--cc=guile-devel@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).