unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Clinton Ebadi <clinton@unknownlamer.org>
To: "Panicz Maciej Godek" <godek.maciek@gmail.com>
Cc: guile-user@gnu.org, Neil Jerram <neiljerram@googlemail.com>
Subject: Re: Simplified slot access in goops
Date: Tue, 02 Dec 2008 15:33:43 -0500	[thread overview]
Message-ID: <87hc5mxqoo.fsf@unknownlamer.org> (raw)
In-Reply-To: <1eb53f5d0812021130u5b41964pa20464a35ce67715@mail.gmail.com> (Panicz Maciej Godek's message of "Tue, 2 Dec 2008 20:30:11 +0100")

"Panicz Maciej Godek" <godek.maciek@gmail.com> writes:

>> 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.
>
> R5RS pattern language allows to create syntactic aliases for practically
> any form. Some time ago I've found the following `let-alias' macro that does
> just this:

Ah, I suspected that syntax-case supported something like this.

> (use-syntax (ice-9 syncase))
>
> (define-syntax let-alias
>   (syntax-rules ()
>     ((_ ((id alias) ...) body ...)
>      (let-syntax ((helper (syntax-rules ()
>                             ((_ id ...) (begin body ...)))))
> 	(helper alias ...)))))
>
> ;; And here's the code for the aforementioned with-object-slots and let-slots:
>
> (use-modules (oop goops))
> (define slot-ref (make-procedure-with-setter slot-ref slot-set!))
>
> (define-syntax with-object-slots (syntax-rules ()
>                                   ((_ (object (alias1  slot1) ...) expr1 ...)
>                                    (let-alias ((alias1 (slot-ref
> object (quote slot1))) ...)
>                                      expr1 ...))
>                                   ((_ (object prop1 ...) expr1 ...)
>                                    (let-alias ((prop1 (slot-ref object
> (quote prop1))) ...)
>                                      expr1 ...))))
>
> (define-syntax let-slots (syntax-rules ()
>                            ((_ () expr1 ...)
>                             (begin expr1 ...))
>                            ((_ (binding1 binding2 ...) expr1 ...)
>                             (with-object-slots binding1
>                                                (let-slots (binding2 ...)
>                                                  expr1 ...)))))

-- 
Ethan: i'm working on myself
Ethan: the self is the most important thing
Ethan: i learned this from a packet of tea




  reply	other threads:[~2008-12-02 20:33 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
2008-12-02 19:30     ` Panicz Maciej Godek
2008-12-02 20:33       ` Clinton Ebadi [this message]
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=87hc5mxqoo.fsf@unknownlamer.org \
    --to=clinton@unknownlamer.org \
    --cc=godek.maciek@gmail.com \
    --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).