From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Optimization & factorization of ‘write’
Date: Wed, 15 Sep 2010 13:40:45 +0200 [thread overview]
Message-ID: <87sk1bgrpe.fsf@gnu.org> (raw)
In-Reply-To: 227537.62931.qm@web37907.mail.mud.yahoo.com
Hi,
Mike Gran <spk121@yahoo.com> writes:
>> From: Ludovic Courtès <ludo@gnu.org>
>
>>
>> > I have a script that I used to check string and char input/output.
>>
>> You mean in addition to the ‘.test’ files?
>
> I have the attached. It is not really a test because it doesn't
> have criteria for right and wrong, but, you can diff the changes
> of the output files after committing to see if output formats
> have stayed the same.
OK, interesting. Any idea how well it covers the display/write code
compared to the test suite?
> But I tried it just now on HEAD, and it triggered a 'glibc detected
> corrupteddouble-linked list' error. Curious.
Hmm indeed. Can you come up with a reduced test case and perhaps a
backtrace or something?
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-09-15 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-14 14:21 Optimization & factorization of ‘write’ Ludovic Courtès
2010-09-14 18:31 ` Mike Gran
2010-09-14 19:12 ` Ludovic Courtès
2010-09-14 23:04 ` Ludovic Courtès
2010-09-15 4:19 ` Mike Gran
2010-09-15 11:40 ` Ludovic Courtès [this message]
2010-09-15 14:28 ` Mike Gran
2010-09-15 21:35 ` Ludovic Courtès
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=87sk1bgrpe.fsf@gnu.org \
--to=ludo@gnu.org \
--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).