From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: fixes to goops + light structs + 'u' slots
Date: Sun, 13 Apr 2008 22:42:55 +0200 [thread overview]
Message-ID: <87ej99mqpc.fsf@gnu.org> (raw)
In-Reply-To: 66e540fe0804131209y6a3a1810i72a6ba048a7cb83b@mail.gmail.com
Hi,
"Mikael Djurfeldt" <mikael@djurfeldt.com> writes:
> 2008/4/13, Ludovic Courtès <ludo@gnu.org>:
>> Yeah. More pragmatically, things like SRFI-9 accessors could be
>> implemented as applicable SMOBS:
>>
>> http://thread.gmane.org/gmane.lisp.guile.devel/6716
>
> I think it's a good idea to read and understand the code before
> planning changes. At least given the state of Guile at the point when
> GOOPS accessors were implemented, the current imlementation was
> superior to both a slot-ref-based and a SMOB-based implementation.
> This is because dispatching a smob took longer time for the evaluator
> than interpreting the current special form-based solution
> (@assert-bound-ref). Note that the current implementation *does*
> compile in the slot position into this form and indeed *has* the
> property which Andy mentions above. Also, SMOB-based accessors would
> be more heavyweight with regard to class creation and memory
> consumption than the current solution.
Sure. Note that my remark and the referred thread dealt with struct and
SRFI-9 record accessors, not with GOOPS.
Thanks for your comment,
Ludovic.
next prev parent reply other threads:[~2008-04-13 20:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 23:45 fixes to goops + light structs + 'u' slots Andy Wingo
2008-04-10 21:33 ` Ludovic Courtès
2008-04-10 23:42 ` Andy Wingo
2008-04-13 18:47 ` Ludovic Courtès
2008-04-13 19:09 ` Mikael Djurfeldt
2008-04-13 20:42 ` Ludovic Courtès [this message]
2008-04-14 21:45 ` Andy Wingo
2008-04-14 22:16 ` Mikael Djurfeldt
2008-04-19 16:28 ` Andy Wingo
2008-04-19 23:07 ` Mikael Djurfeldt
2008-04-20 10:46 ` Andy Wingo
2008-04-14 22:20 ` Mikael Djurfeldt
2008-04-15 22:22 ` Andy Wingo
2008-04-16 6:34 ` Mikael Djurfeldt
2008-04-16 6:52 ` 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=87ej99mqpc.fsf@gnu.org \
--to=ludo@gnu.org \
--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).