From: Mike Gran <spk121@yahoo.com>
To: Guile Devel <guile-devel@gnu.org>
Subject: Sting abstraction 2
Date: Wed, 20 May 2009 08:24:09 -0700 [thread overview]
Message-ID: <1242833049.32575.7271.camel@localhost.localdomain> (raw)
Hi-
I've been working on the Unicode problem in Guile, and I had been too
ambitious. I hacked it up pretty harsh and started getting errors that
were tough to debug.
Anyway, I backtracked a bit. Today I pushed a new tree
(string_abstraction2) which should be the same as master except with all
unnecessary calls to scm_i_string_chars, scm_i_symbol_chars, and
scm_i_string_writable_chars removed. I largely avoided other
unnecessary modifications. It is still an 8-bit string build, but, now
the string internals have been confined to strings.c and strports.c,
with very few exceptions.
>From here, I'm more confident that I can fold in changes for unicode
without breakage.
next reply other threads:[~2009-05-20 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 15:24 Mike Gran [this message]
2009-05-20 21:11 ` Sting abstraction 2 Ludovic Courtès
2009-05-20 22:49 ` Mike Gran
2009-05-20 23:32 ` Ludovic Courtès
2009-05-21 3:33 ` Mike Gran
2009-05-22 15:59 ` Andy Wingo
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=1242833049.32575.7271.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).