From: Neil Jerram <neiljerram@gmail.com>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: GOOPS:Can I just overload "slot-set!" under #:virtual and let alone "slot-ref" ?
Date: Thu, 2 Dec 2010 17:40:52 +0000 [thread overview]
Message-ID: <AANLkTi=fbQqWNDQ44f7CDXaKat4+d3gF5-y9NWdvrvm8@mail.gmail.com> (raw)
In-Reply-To: <AANLkTindzR+E5mwuik66JAUEak7qq7o_9q1se5OqinV8@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]
On 2 December 2010 07:06, Nala Ginrut <nalaginrut@gmail.com> wrote:
> Hi, everybody!
> I got a question while I'm trying GOOPS, here is some example code pieces:
> ;;guile code
> (define-class <test> ()
> (cache #:init-form 0)
> (tt #:init-form 1
> #:allocation #:virtual
> #:slot-set! (lambda (o v)
> (slot-set! o 'cache
> (cons v (slot-ref o 'cache)))
> );;end lambda
> #:slot-ref (lambda (o) #f) ;; ***FIXME: can I use generic "slot-ref"
> without re-define here??
> ..........
> ;;guile code end
> -----------------------------------------------
>
> Please notice the line with "***FIXME" .I know that the "slot-set!" and
> "slot-ref" must be re-defined under "#:allocation #:virtual", but can I find
> some approach that just re-define one of them? Maybe I'll need a
> modified(with overload) "slot-set!", but I need a generic "slot-ref" in some
> circumstance. I don't know how to do. If I called "slot-ref" in the
> re-defination of "slot-ref", that would be recursively infinite.
> How can I deal with this? Any help will be appreciated, thanks!
>
I'm not sure this is what you mean... but yes, your #:slot-ref lambda can do
a slot-ref on normal slots, such as "cache", e.g.:
#:slot-ref (lambda (o) (car (slot-ref o 'cache)))
Neil
[-- Attachment #2: Type: text/html, Size: 1779 bytes --]
next prev parent reply other threads:[~2010-12-02 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 7:06 GOOPS:Can I just overload "slot-set!" under #:virtual and let alone "slot-ref" ? Nala Ginrut
2010-12-02 17:40 ` Neil Jerram [this message]
2010-12-03 0:52 ` Nala Ginrut
2010-12-03 1:42 ` Neil Jerram
2010-12-03 2:13 ` Nala Ginrut
2010-12-03 18:22 ` Neil Jerram
2010-12-12 9:42 ` nalaginrut
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='AANLkTi=fbQqWNDQ44f7CDXaKat4+d3gF5-y9NWdvrvm8@mail.gmail.com' \
--to=neiljerram@gmail.com \
--cc=guile-user@gnu.org \
--cc=nalaginrut@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).