unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Kjetil S. Matheussen" <k.s.matheussen@notam02.no>
To: Maciek Godek <pstrychuj@gmail.com>, guile-user@gnu.org
Subject: Re: Closure?
Date: Mon, 14 Jul 2008 23:41:22 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0807142318050.5269@ttleush> (raw)
In-Reply-To: <e2ceda030807141414i5acef7d1h37d12d14e01cc1d@mail.gmail.com>



On Mon, 14 Jul 2008, Maciek Godek wrote:

> Kjetil S. Matheussen:
>
>> I think local-eval is necessary for making
>> a namespace system of the below type without having to use
>> codewalking macros to expand the bodies of functions:
>>
>> (define-namespace bank)
>> (def-bank sum 0)
>> (def-bank (add n)
>>  (set! sum (+ n sum)) ;; Note that it's enough to write "sum".
>>
>> (bank.add 50)
>> bank.sum
>> => 50
>
> This certainly looks like trashing global namespace
> (which isn't good in the long run) and doesn't allow you
> to have object handlers (like many variables referring
> to the same object) without additional quirks.
>

It's just an example of what local-eval can
be good for. It's an example of a _namespace
system_, and not an _OO system_.



>> But for implementing a message passing OO system,
>> it's easier to use macros and hash tables, plus
>> that it probably performs much better:
>
> Pefrorms better than local-eval or better than
> define-namespace?
>

It's much faster than local-eval since it's not
calling eval for each method call. The overhead of calling
a method in an OO system, based on hash tables
and macros, is basically just the time it takes looking
up the address of the function from
a hash-table. For guile, which has a large
overhead already, your program probably won't
go any slower doing this compared to calling
functions directly:


(define (make-bank sum)
   (let ((attributes (make-hash-table)))
     (define dispatcher
       (lambda (which . rest)
         (apply (hashq-ref attributes which) rest)))
     (hashq-set! attributes 'sum (lambda ()
                                   sum))
     (hashq-set! attributes 'add (lambda (n)
                                   (set! sum (+ n sum))))
     dispatcher))

(define bank (make-bank 0))
(bank 'add 2)
(bank 'sum)
=> 2


And by using some macros, you can make the syntax look
much prettier.




>> (def-class <bank>
>>   (def-var sum 0)
>>   (def-method (add n)
>>      (set! sum (+ n sum)))
>>
>> (define bank (new <bank>))
>> (-> bank add 50)
>> (-> bank sum)
>> => 50
>>
>> There's a bunch of these systems for scheme.
>> The syntax above is used from
>> http://snd.cvs.sourceforge.net/snd/cvs-snd/oo.scm?view=log
>>
>> Guile's own OO system called GOOPS is also very nice.
>> GOOPS a quite verbose but very powerful and a lot
>> more interactive. It's similar to CL's CLOS, which
>> you should look at if you are not familiar with
>> already.
>
> Well, I've read some documentation of GOOPS and then
> I took a glimpse at its source. It has at least a few
> disadvantages, for it is an object system implemented in
> scheme -- it is therefore hard to access its objects from C
> (while closures are easily accessible through
> scm_local_eval) and it probably won't run as fast as
> local-eval, at least conceptually.
>

local-eval is forced to interpret its argument, and is therefore, at least 
conceptually, very slow. I very much doubt GOOPS is that slow,
but I don't know how GOOPS is implemented though. :-)





  parent reply	other threads:[~2008-07-14 21:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cmu-lmtpd-15105-1216051603-3@mail-imap1.uio.no>
2008-07-14 16:30 ` Closure? Kjetil S. Matheussen
2008-07-14 21:14   ` Closure? Maciek Godek
     [not found]   ` <e2ceda030807141414i5acef7d1h37d12d14e01cc1d@mail.gmail.com>
2008-07-14 21:41     ` Kjetil S. Matheussen [this message]
2008-07-14 22:46       ` Closure? Maciek Godek
     [not found] <cmu-lmtpd-26382-1215792454-10@mail-imap1.uio.no>
2008-07-11 17:42 ` Closure? Kjetil S. Matheussen
2008-07-11 17:47   ` Closure? Kjetil S. Matheussen
2008-07-11 20:54     ` Closure? Maciek Godek
2008-07-12 11:47       ` Closure? Kjetil S. Matheussen
2008-07-13  6:59         ` Closure? Maciek Godek
2008-07-12 22:43     ` Closure? Neil Jerram
2008-07-15  7:59       ` Closure? Ludovic Courtès
2008-07-15  9:11         ` Closure? Andy Wingo
2008-07-16 16:42           ` Closure? Ludovic Courtès
2008-07-11 14:48 Closure? Maciek Godek
2008-07-11 15:01 ` Closure? Ludovic Courtès
2008-07-11 15:32   ` Closure? Maciek Godek
2008-07-12 22:57 ` Closure? Neil Jerram
2008-07-13  6:57   ` Closure? Maciek Godek
2008-07-13 22:56     ` Closure? Neil Jerram
2008-07-14  1:15       ` Closure? Maciek Godek

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=Pine.LNX.4.64.0807142318050.5269@ttleush \
    --to=k.s.matheussen@notam02.no \
    --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).