From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: guile-devel@gnu.org
Subject: Re: substantial performance loss when running long-lived or computationally intensive programs
Date: Wed, 14 May 2003 16:36:47 +0200 [thread overview]
Message-ID: <xy7el318uio.fsf@nada.kth.se> (raw)
In-Reply-To: <16066.9478.131532.331041@localhost.localdomain> (Han-Wen Nienhuys's message of "Wed, 14 May 2003 13:14:14 +0200")
Han-Wen Nienhuys <hanwen@cs.uu.nl> writes:
> One thing that does nag me, is code in srcprop.c that manipulates
> scm_mallocated directly and doesn't call
> scm_gc_register_collectable_memory(). Is there a good reason for this?
Nope. Only that scm_gc_register_collectable_memory() didn't exist
when srcprop.c was written in 1996. In fact, at that time, direct
manipulation was probably the only possibility.
Please feel free to change this.
M
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-14 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 3:36 substantial performance loss when running long-lived or computationally intensive programs Michael A. Wells
2003-05-14 11:14 ` Han-Wen Nienhuys
2003-05-14 14:36 ` Mikael Djurfeldt [this message]
2003-05-15 23:10 ` Han-Wen Nienhuys
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=xy7el318uio.fsf@nada.kth.se \
--to=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).