From: Neil Jerram <neil@ossau.uklinux.net>
To: Mike Gran <spk121@yahoo.com>
Cc: guile-devel@gnu.org
Subject: Re: Wide strings
Date: Fri, 30 Jan 2009 00:15:44 +0000 [thread overview]
Message-ID: <873af1myxb.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <87iqnz6kv5.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu\, 29 Jan 2009 01\:01\:34 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
>>> Do we need to talk more about what needs to be accomplished? Do we
>>> need a complete specification? Do we need a vote on if it is a good
>>> idea?
>>
>> I think you're going in the right direction. More importantly, although
>> I can't speak for them, Neil and Ludo seem to think so too.
>
> Yes, as far as I'm concerned. I know you're probably more knowledgeable
> than I am on this issue and I'm confident.
For the record, I'm happy too - in fact I'm excited that Guile is
finally going to have wide strings. Technically I think I'm less of
an expert here than everyone else who has commented, so I'm happy to
defer to the apparent consensus. I see that Clinton's idea goes
beyond that, but (IIUC) it looks like we doesn't lose anything by
going with Latin-1/UCS-32 now, and then Clinton's idea could be added
later; is that correct?
Regards,
Neil
next prev parent reply other threads:[~2009-01-30 0:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 21:15 Wide strings Mike Gran
2009-01-25 22:31 ` Ludovic Courtès
2009-01-25 23:32 ` Neil Jerram
2009-01-26 20:24 ` Ludovic Courtès
2009-01-26 0:16 ` Mike Gran
2009-01-26 15:21 ` Mike Gran
2009-01-26 21:40 ` Ludovic Courtès
2009-01-27 5:38 ` Mike Gran
2009-01-27 5:52 ` Mike Gran
2009-01-27 9:50 ` Andy Wingo
2009-01-27 18:59 ` Ludovic Courtès
2009-01-28 16:44 ` Mike Gran
2009-01-28 18:36 ` Andy Wingo
2009-01-29 0:01 ` Ludovic Courtès
2009-01-30 0:15 ` Neil Jerram [this message]
2009-01-28 20:44 ` Clinton Ebadi
2009-01-28 23:49 ` 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=873af1myxb.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).