From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: Wide characters support
Date: Thu, 25 Aug 2005 22:31:20 +0300 [thread overview]
Message-ID: <87oe7l4xvb.fsf@zagadka.de> (raw)
In-Reply-To: <8764tujwmm.fsf@laas.fr> (Ludovic Courtès's message of "Thu, 25 Aug 2005 09:36:49 +0200")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
> Marius Vollmer <mvo@zagadka.de> writes:
>
>> Well, my current plans are to get us Unicode support by having three
>> kinds of strings, with three widths (8, 16 and 32 bits, of course).
>> But they are not very concrete. I am not thinking about using
>> wchar_t.
>
> Because of its potential greediness in terms of memory consumption?
Yes, but mostly because I think the type is not really an important
ingredient when using Unicode exclusively, since we know concretely
what we want and don't need to rely on wchar_t as a portability aid.
(There will of course be functions to convert Guile strings into
wchar_t arrays.)
One of the goals of moving SRFI 13 and 14 into the core was to
discourage people from relying on the internal representation of
strings. This means that this internal representation can be changed
more easily, for example, to a multibyte encoding or to use splay
trees, etc.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-08-25 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 12:22 Wide characters support Ludovic Courtès
2005-08-24 20:28 ` Marius Vollmer
2005-08-25 7:36 ` Ludovic Courtès
2005-08-25 19:31 ` Marius Vollmer [this message]
2005-08-26 7:37 ` Ludovic Courtès
2005-08-26 19:00 ` Marius Vollmer
2005-08-28 23:30 ` Han-Wen Nienhuys
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=87oe7l4xvb.fsf@zagadka.de \
--to=mvo@zagadka.de \
--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).