From: Mike Gran <spk121@yahoo.com>
To: Guile Devel <guile-devel@gnu.org>
Subject: Wide strings and the VM
Date: Sun, 26 Jul 2009 15:22:23 -0700 [thread overview]
Message-ID: <1248646943.787.45.camel@localhost.localdomain> (raw)
Hi-
I wonder if I could get someone to check out what I've done with wide
strings and the VM on the string_abstraction2 branch with commit
efb042...
That code is quite confusing, and I may have made a mess of it. And, I
wasn't sure about alignment.
I daresay that this Unicode string stuff is now a genuine alpha. It is
feature complete: wide chars, wide strings and symbols, Unicode-capable
SRFI-14, and VM / compiler updates.
Unicode capable regex will, unfortunately, have to wait until
libunistring finishes their implementation.
Still have old ideas from Andy to incorporate, though. More testing, of
course. And some speed improvements are probably necessary.
--Mike
reply other threads:[~2009-07-26 22:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1248646943.787.45.camel@localhost.localdomain \
--to=spk121@yahoo.com \
--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).