From: Neil Jerram <neil@ossau.uklinux.net>
Cc: djurfeldt@nada.kth.se, guile-devel@gnu.org
Subject: Re: goops and memoization
Date: 29 Nov 2002 23:31:51 +0000 [thread overview]
Message-ID: <m365ug7y1k.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <m3d6oo801c.fsf@laruns.ossau.uklinux.net>
>>>>> "Neil" == Neil Jerram <neil@ossau.uklinux.net> writes:
Neil> If this is correct, the fix is to pass `x' through your memoizer just
Neil> before `goto nontoplevel_begin;', like this:
Neil> apply_cmethod: /* inputs: z, arg1 */
Neil> {
Neil> SCM formals = SCM_CMETHOD_FORMALS (z);
Neil> env = EXTEND_ENV (formals, arg1, SCM_CMETHOD_ENV (z));
Neil> x = SCM_CMETHOD_BODY (z);
Neil> x = memoize (x); /* ADDED */
Neil> goto nontoplevel_begin;
Neil> }
And to follow up immediately to myself ... actually this is suboptimal
because it means that even a cached method is memoized every time it
is called. (Also I was wrong about the lambda; the expression
returned by scm_memoize_method doesn't begin with a lambda.)
What we should really do is memoize before the method is installed
into the method cache. I think the place for this is in
compute-entry-with-cmethod in oop/goops/compile.scm: just before
`(cons entry place-holder)':
(define (compute-entry-with-cmethod methods types)
(or (code-table-lookup (slot-ref (car methods) 'code-table) types)
(let* ((method (car methods))
(place-holder (list #f))
(entry (append types place-holder)))
;; In order to handle recursion nicely, put the entry
;; into the code-table before compiling the method
(slot-set! (car methods) 'code-table
(cons entry (slot-ref (car methods) 'code-table)))
(let ((cmethod (compile-method methods types)))
(set-car! place-holder (car cmethod))
(set-cdr! place-holder (cdr cmethod)))
(set-cdr! (cdr place-holder) ; ADDED
(memoize (cdr place-holder))) ; ADDED
(cons entry place-holder))))
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-11-29 23:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 13:41 goops and memoization Dirk Herrmann
2002-11-17 10:56 ` Neil Jerram
2002-11-20 18:11 ` Dirk Herrmann
2002-11-21 3:11 ` Mikael Djurfeldt
2002-11-21 3:28 ` Mikael Djurfeldt
2002-11-21 23:50 ` Neil Jerram
2002-11-22 1:08 ` Mikael Djurfeldt
2002-11-22 1:13 ` Mikael Djurfeldt
2002-11-24 9:41 ` Neil Jerram
2002-11-24 16:32 ` Mikael Djurfeldt
2002-11-21 20:31 ` Neil Jerram
2002-11-22 0:49 ` Mikael Djurfeldt
2002-11-29 22:48 ` Neil Jerram
2002-11-29 23:31 ` Neil Jerram [this message]
2002-11-21 20:36 ` Neil Jerram
2002-11-24 16:42 ` Dirk Herrmann
[not found] <Pine.GSO.4.05.10212011757340.18607-100000@sallust.ida.ing.tu-bs.de>
2002-12-01 18:00 ` Neil Jerram
2002-12-02 8:45 ` Mikael Djurfeldt
2002-12-02 9:14 ` Mikael Djurfeldt
2002-12-03 0:13 ` Lynn Winebarger
2002-12-03 7:59 ` Mikael Djurfeldt
2002-12-03 8:38 ` Tom Lord
2002-12-04 2:25 ` Mikael Djurfeldt
2002-12-04 2:49 ` Tom Lord
2002-12-03 17:17 ` Lynn Winebarger
2002-12-04 2:41 ` Mikael Djurfeldt
[not found] <Pine.GSO.4.05.10212021650410.21423-100000@sallust.ida.ing.tu-bs.de>
2002-12-04 1:53 ` Mikael Djurfeldt
2002-12-04 2:38 ` Tom Lord
2002-12-04 2:56 ` Rob Browning
[not found] <Pine.GSO.4.05.10212021836430.21423-100000@sallust.ida.ing.tu-bs.de>
2002-12-04 2:19 ` Mikael Djurfeldt
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=m365ug7y1k.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=djurfeldt@nada.kth.se \
--cc=guile-devel@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).