unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: "Maciek Godek" <pstrychuj@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Simplified slot access in goops
Date: Sat, 28 Aug 2010 13:07:04 -0700	[thread overview]
Message-ID: <m38w3q33iv.fsf@unquote.localdomain> (raw)
In-Reply-To: <e2ceda030811271236q5ec79d6l21305d3584b0bf@mail.gmail.com> (Maciek Godek's message of "Thu, 27 Nov 2008 21:36:30 +0100")

Hi Maciek,

I know its been a couple years, but you raised an interesting point that
Guile wasn't really able to handle at that point. Your implementation of
`in' (commonly known as `with-slots', I believe) follows the mail.

On Thu 27 Nov 2008 12:36, "Maciek Godek" <pstrychuj@gmail.com> writes:

> (use-modules (oop goops))
> (use-syntax (ice-9 syncase))

With Guile 2.0 (coming shortly!), there is no more need to use ice-9
syncase.

> 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

The problem with this macro is that `o' can be of any type at all, but
Guile needs to know at least whether a given identifier is a macro or a
local variable or what, at expansion time.

So for that reason, with-slots usually takes a list of slots, explicitly:

  (with-slots o (a b c)
    (set! a 5)
    (set! b (1+ a))
    (set! c (+ a b))
    (+ a b c))

It would be possible to pass the class instead, but then the class would
need to be known at compile-time, and you run into a number of issues
there. Anyway, here's that with-slots definition:

  (define-syntax with-slots
    (syntax-rules ()
      ((_ obj (slot ...) b b* ...)
       (let-syntax
           ((slot (identifier-syntax
                    (id (slot-ref obj 'slot))
                    ((set! id val) (slot-set! obj 'slot val))))
            ...)
         b b* ...))))
           
Here we use the new settable identifier-syntax.

Note that slot-ref / slot-set isn't the most efficient way to reference
slots; the best thing is to use accessors, which JIT-compile (sorta) to
struct-ref opcodes, but we don't know that accessors exist for these
slots. You can define a with-accessors macro though, that does assume
accessors are available.

In fact with more assumptions, it's possible to compile to struct-ref /
struct-set yourself -- see the examples in the "Syntax" chapter of "The
Scheme Programming Language" 4th edition (available online) for an
illuminating take on the issue.

Cheers,

Andy

The original definition:

> (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) ...)))))
>

-- 
http://wingolog.org/



  parent reply	other threads:[~2010-08-28 20:07 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
2010-08-28 20:07 ` Andy Wingo [this message]
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=m38w3q33iv.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=guile-user@gnu.org \
    --cc=pstrychuj@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).