From: Kevin Ryde <user42@zip.com.au>
Subject: Re: [PATCH] Fixed `scm_i_take_stringbufn ()'
Date: Thu, 16 Feb 2006 09:15:11 +1100 [thread overview]
Message-ID: <877j7wp8uo.fsf@zip.com.au> (raw)
In-Reply-To: <878xsdnj8l.fsf@laas.fr> (Ludovic Courtès's message of "Wed, 15 Feb 2006 09:01:30 +0100")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
>
> a periodic distribution whose period is unknown
The idea is to force gc's before and after, expecting mem counters to
be unchanged by the test code in the middle. I had to setup for
multiple attempts, I guess memoizing or other freaky stuff happens on
the first couple of goes.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2006-02-15 22:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 16:38 [PATCH] Fixed `scm_i_take_stringbufn ()' Ludovic Courtès
2006-02-13 21:38 ` Kevin Ryde
2006-02-14 9:47 ` Ludovic Courtès
2006-02-15 0:38 ` Kevin Ryde
2006-02-15 7:58 ` Ludovic Courtès
2006-02-15 22:03 ` Kevin Ryde
2006-02-21 8:37 ` Ludovic Courtès
2006-02-15 0:48 ` Kevin Ryde
2006-02-15 8:01 ` Ludovic Courtès
2006-02-15 22:15 ` Kevin Ryde [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=877j7wp8uo.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).