From: Clinton Ebadi <clinton@unknownlamer.org>
To: "Neil Jerram" <neiljerram@googlemail.com>
Cc: guile-user@gnu.org
Subject: Re: Simplified slot access in goops
Date: Tue, 02 Dec 2008 04:32:24 -0500 [thread overview]
Message-ID: <87ljuyylav.fsf@unknownlamer.org> (raw)
In-Reply-To: <49dd78620812011425k2720df81tbf3820b429ba7ba@mail.gmail.com> (Neil Jerram's message of "Mon, 1 Dec 2008 22:25:30 +0000")
"Neil Jerram" <neiljerram@googlemail.com> writes:
> 2008/11/27 Maciek Godek <pstrychuj@gmail.com>:
>
>> Perhaps the possible inconvenience is that all variable
>> names that happen to be the slot names of a given class
>> are shadowed. In the long run it may also cause significant
>> performance problems (or that's what I think), especially
>> when dealing with objects with a hell lotta slots.
>>
>> I wonder if it would be possible to make it optimizable
>> for the JIT compiler somehow (and to make the "in" syntax
>> official part of GOOPS)
>
> I think this is a nice interface; but I'm less sure about the
> implementation. Why do you need to use primitive-eval at all?
>
> Isn't CL's with-slots a bit like this? It might help to look at how
> that is implemented.
with-slots uses symbol-macrolet[0] to bind each of the variable names to
symbol macros within its body. I don't know of anything in Guile that is
equivalent.
[0] http://franz.com/support/documentation/6.0/ansicl/dictentr/symbol-m.htm
--
Ruled by the ebb of my oceans
Slaves to the dusk and the dawn
Your petri dish civilisations
Are buried and born
next prev parent reply other threads:[~2008-12-02 9:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 20:36 Simplified slot access in goops Maciek Godek
2008-11-28 18:41 ` Panicz Maciej Godek
2008-12-01 22:25 ` Neil Jerram
2008-12-02 9:32 ` Clinton Ebadi [this message]
2008-12-02 19:30 ` Panicz Maciej Godek
2008-12-02 20:33 ` Clinton Ebadi
2010-08-28 20:07 ` Andy Wingo
2010-08-29 0:22 ` Panicz Maciej Godek
2010-08-29 0:56 ` 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=87ljuyylav.fsf@unknownlamer.org \
--to=clinton@unknownlamer.org \
--cc=guile-user@gnu.org \
--cc=neiljerram@googlemail.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).