From: Andy Wingo <wingo@pobox.com>
To: Mike Gran <spk121@yahoo.com>
Cc: Guile Devel <guile-devel@gnu.org>
Subject: Re: Unicode-capable srfi-14 charsets (f49dbcadf...)
Date: Thu, 27 Aug 2009 23:23:56 +0200 [thread overview]
Message-ID: <m3ocq1t0gj.fsf@pobox.com> (raw)
In-Reply-To: <1251386430.17414.11.camel@localhost.localdomain> (Mike Gran's message of "Thu, 27 Aug 2009 08:20:30 -0700")
On Thu 27 Aug 2009 17:20, Mike Gran <spk121@yahoo.com> writes:
> I pushed the commit for Unicode-capable srfi-14. Of all parts necessary
> for Unicode, this patch has the largest amount of new code and is most
> likely to cause compilation problems.
On Linux, this now works fine for me; make succeeds, one test fails for
me (utf8 r6rs ports).
On Mac 10.5, I get an exception running the test suite, which actually
stops the test suite: bad argument to setlocale. I don't recall which
file that was in. Apologies for the imprecision, that machine is at
work.
> Since the default charsets such as char-set:lower-case are much larger
> in the Unicode scenario, I had to change both the underlying
> structures that hold them as well as the print format. I also had to
> pregenerate them, since it was too slow to create them at startup. So
> this is also the part of this project where I've taken the greatest
> liberties.
Looks good to me. Ideally over time these will migrate to being
implemented in Scheme. For now, please make that static table const, so
it can be shared between processes, and avoid some relocations at link
time.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2009-08-27 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 15:20 Unicode-capable srfi-14 charsets (f49dbcadf...) Mike Gran
2009-08-27 21:23 ` Andy Wingo [this message]
2009-08-27 21:32 ` Andy Wingo
2009-08-27 23:19 ` 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=m3ocq1t0gj.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=spk121@yahoo.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).