From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Reducing iconv-induced memory usage
Date: Sat, 07 May 2011 22:51:39 +0200 [thread overview]
Message-ID: <87bozefd44.fsf@gnu.org> (raw)
In-Reply-To: 87vcxnhke8.fsf@gnu.org
Hello!
ludo@gnu.org (Ludovic Courtès) writes:
> Hello,
>
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Here’s an updated patch that strictly checks for ill-formed UTF-8
>> sequences, as Mark pointed out. It passes all the tests I recently
>> added to ports.test.
>
> I committed it, though Mark rightfully noted on IRC a non-conformance
> issue. I’ve added a FIXME and started looking into it.
Commit 7be1705dbda377780335ecbcbfce04de523f2671 fixes it, AFAICS.
Mark, please let me know if you spot other errors!
Thanks,
Ludo’.
prev parent reply other threads:[~2011-05-07 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 21:10 Reducing iconv-induced memory usage Ludovic Courtès
2011-04-26 22:41 ` Ludovic Courtès
2011-04-27 3:47 ` Mark H Weaver
2011-04-27 14:36 ` Ludovic Courtès
2011-05-05 16:19 ` Ludovic Courtès
2011-05-06 16:19 ` Ludovic Courtès
2011-05-07 20:51 ` Ludovic Courtès [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=87bozefd44.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).