From: Mike Gran <spk121@yahoo.com>
To: Andy Wingo <wingo@pobox.com>
Cc: Guile Devel <guile-devel@gnu.org>
Subject: Re: string_abstraction2 review
Date: Sun, 19 Jul 2009 08:02:35 -0700 [thread overview]
Message-ID: <1248015755.3865.12.camel@localhost.localdomain> (raw)
In-Reply-To: <m3my8e1nl8.fsf@pobox.com>
On Thu, 2009-06-11 at 23:12 +0200, Andy Wingo wrote:
> Howdy good sir!
>
I'm back on task. I'll go through your comments from the review of a
month or so ago, and try to push the Unicode stuff next week. Things
seem stable on my end, but, some optimization work remains to be done.
With respect to srfi-14 and char-sets, I wrote a new, Unicode capable,
one. It is a big change, though, which might make some uneasy. It is
in C for now, but, it certainly could go pure scheme at some point.
Using what I learned from writing the C version, I have a half-completed
version of the same in scheme as well.
The only necessary action item remaining on my srfi-14 is to hardcode
the standard char sets instead of populating them at startup, which
takes a non-trivial amount of time.
Thanks,
Mike
prev parent reply other threads:[~2009-07-19 15:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 21:12 string_abstraction2 review Andy Wingo
2009-06-12 0:20 ` Andreas Rottmann
2009-07-19 15:02 ` Mike Gran [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=1248015755.3865.12.camel@localhost.localdomain \
--to=spk121@yahoo.com \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).