From: "Maciek Godek" <pstrychuj@gmail.com>
To: guile-user@gnu.org
Subject: Simplified slot access in goops
Date: Thu, 27 Nov 2008 21:36:30 +0100 [thread overview]
Message-ID: <e2ceda030811271236q5ec79d6l21305d3584b0bf@mail.gmail.com> (raw)
Hi,
Below is a simple set of functions and macros to make
the access to goops object properties easier:
(use-modules (oop goops))
(use-syntax (ice-9 syncase))
(define-syntax let-alias
(syntax-rules ()
((_ ((id alias) ...) body ...)
(let-syntax ((helper (syntax-rules ()
((_ id ...) (begin body ...)))))
(helper alias ...)))))
(define slot (make-procedure-with-setter slot-ref slot-set!))
(define-syntax in (syntax-rules ()
((_ object expr ...)
(primitive-eval
(list 'let-alias
(map (lambda(s)(list(car s)(list 'slot object (list 'quote (car s)))))
(class-slots (class-of object)))
(quote expr) ...)))))
Now suppose we have an instance of a class:
(define-class C ()
a b c)
(define o (make C))
Using the "in" macro, we can write:
(in o
(set! a 5)
(set! b (1+ a))
(set! c (+ a b))
(+ a b c))
=> 22
which is more convenient than:
(slot-set! o 'a 5)
(slot-set! o 'b (1+ (slot-ref o 'a))
(slot-set! o 'c (+ (slot-ref o 'a) (slot-ref o 'b)))
(+ (slot-ref o 'a) (slot-ref o 'b) (slot-ref o 'c))
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)
Sincerely,
M.
next reply other threads:[~2008-11-27 20:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 20:36 Maciek Godek [this message]
2008-11-28 18:41 ` Simplified slot access in goops Panicz Maciej Godek
2008-12-01 22:25 ` Neil Jerram
2008-12-02 9:32 ` Clinton Ebadi
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=e2ceda030811271236q5ec79d6l21305d3584b0bf@mail.gmail.com \
--to=pstrychuj@gmail.com \
--cc=guile-user@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).