From: Matt Wette <matt.wette@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: String internals sketch
Date: Fri, 10 Mar 2017 16:30:41 -0800 [thread overview]
Message-ID: <1D6E805B-EC15-491D-AD8F-C8F6212DA54B@gmail.com> (raw)
In-Reply-To: <87efy52lnp.fsf@fencepost.gnu.org>
> On Mar 10, 2017, at 7:31 AM, David Kastrup <dak@gnu.org> wrote:
> I've been mulling a bit over enabling UTF-8 as an internal string
> representation. There are several interesting points to consider:
One point to consider on this topic is that guile is targeted (via the compiler tower) to support other languages. Strings in ecmascript, for example, are 16-bit code points, not 8 or 32. I personally don’t care that the guile-2.2 hosted ecmascript can’t be a pedantic implementation, but it may generate issues so some down the road. (BTW, the other area in which guile does not implement ecmascript is in representation of numbers
next prev parent reply other threads:[~2017-03-11 0:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 15:31 String internals sketch David Kastrup
2017-03-10 16:08 ` Andy Wingo
2017-03-10 16:51 ` David Kastrup
2017-03-15 15:46 ` David Kastrup
2017-03-11 0:30 ` Matt Wette [this message]
2017-03-11 6:44 ` David Kastrup
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=1D6E805B-EC15-491D-AD8F-C8F6212DA54B@gmail.com \
--to=matt.wette@gmail.com \
--cc=dak@gnu.org \
--cc=guile-user@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).