From: Mikael Djurfeldt <mdj@kvast.blakulla.net>
Cc: Neil Jerram <neil@ossau.uklinux.net>,
Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de>,
guile-devel@gnu.org, djurfeldt@nada.kth.se
Subject: Re: goops and memoization
Date: Thu, 21 Nov 2002 20:13:04 -0500 [thread overview]
Message-ID: <xy7isyq2yqn.fsf@linnaeus.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <xy7lm3m2yz2.fsf@linnaeus.i-did-not-set--mail-host-address--so-tickle-me> (Mikael Djurfeldt's message of "Thu, 21 Nov 2002 20:08:01 -0500")
Mikael Djurfeldt <mdj@kvast.blakulla.net> writes:
>> Given the gf and specializers, call-next-method works out a list of
>> applicable methods (probably cached) in the same way as for a normal
>> gf application, then it looks through this list for m and applies the
>> method after m to the supplied arguments (formals).
[...]
> Are you saying that you'd want to compute the list of applicable
> methods at every call to (next-method)? That way overhead per call
> would become O(NM) where N is the number of applicable methods and M
> the maximum length of argument lists.
Oops, didn't see that you wrote "probably cached". But if you mean in
the same way as in gf application your suggested approach wouldn't
work because the list of applicable methods is unique per application
arglist signature and gf application also caches per application, not
per method definition.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-11-22 1:13 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 [this message]
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
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=xy7isyq2yqn.fsf@linnaeus.i-did-not-set--mail-host-address--so-tickle-me \
--to=mdj@kvast.blakulla.net \
--cc=dirk@sallust.ida.ing.tu-bs.de \
--cc=djurfeldt@nada.kth.se \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
/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).