From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: djurfeldt@nada.kth.se
Subject: Re: memory costs of storing lambdas? (correction)
Date: Thu, 01 May 2003 13:38:52 +0200 [thread overview]
Message-ID: <xy7ptn26gmr.fsf_-_@nada.kth.se> (raw)
In-Reply-To: <xy7u1cf57r1.fsf@nada.kth.se> (Mikael Djurfeldt's message of "Thu, 01 May 2003 11:36:02 +0200")
Mikael Djurfeldt <djurfeldt@nada.kth.se> writes:
> In your case, you also surround the closure with an environment
> captured by the closure. This environment has the structure
> (explained in the Guile docs):
>
> new-env = < frame, env >
> frame = < formals, values >
> formals = < 'style, '() >
> values = < style-value, '() >
>
> So, you have 4 pairs for the environment
Oops. The `formals' pair is constant, so it doesn't add to the cost
of new environments.
> So, in total, the object returned by `style-setter' above will
> consume 12
Rather 11, then.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2003-05-01 11:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 11:06 memory costs of storing lambdas? Han-Wen Nienhuys
2003-05-01 9:36 ` Mikael Djurfeldt
2003-05-01 11:38 ` Mikael Djurfeldt [this message]
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=xy7ptn26gmr.fsf_-_@nada.kth.se \
--to=djurfeldt@nada.kth.se \
/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).