From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Unicode ports patch
Date: Tue, 01 Sep 2009 20:25:26 +0200 [thread overview]
Message-ID: <m3k50i34kp.fsf@pobox.com> (raw)
In-Reply-To: <87hbvnnkl8.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 01 Sep 2009 10:19:15 +0200")
Hi,
On Tue 01 Sep 2009 10:19, ludo@gnu.org (Ludovic Courtès) writes:
> Mike Gran <spk121@yahoo.com> writes:
>
>> The latest commit 'Add full Unicode capability to ports and the default
>> reader' 889975e51accb80491af76fc5db980aeb3edd342 adds the majority of
>> the functionality for non-ASCII strings.
>
> This patch adds a few functions related to string ports:
>
> * libguile/strports.c: store string ports in locale encoding
> (scm_strport_to_locale_u8vector, scm_call_with_output_locale_u8vector)
> (scm_open_input_locale_u8vector, scm_get_output_locale_u8vector):
> new functions
>
> I think it would be nicer if these used bytevectors instead of u8vectors
> and were locale-independent (which would match the `string->utf8' &
> co. API). Also I would make `scm_strport_to_locale_u8vector ()'
> private. And finally, it'd be even better if it were documented in the
> manual. :-)
>
> Actually I'm not convinced that `call-with-output-locale-*' and
> `open-input-locale-*' are useful, precisely because we can use a string
> port to get a string and then `string->utf8' to get at the string bits.
FWIW, I think I agree with all of Ludovic's comments; though if there is
a way that we can simply arrange to output bytes to an R6RS binary
output port, I think there are already efficient means to collect the
bytes from such a port in a bytevector.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2009-09-01 18:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 15:06 Unicode ports patch Mike Gran
2009-08-25 19:54 ` dsmich
2009-08-25 19:58 ` Andy Wingo
2009-09-01 8:19 ` Ludovic Courtès
2009-09-01 18:25 ` Andy Wingo [this message]
2009-09-01 19:19 ` Mike Gran
2009-09-01 19:34 ` Ludovic Courtès
2009-09-01 21:08 ` Mike Gran
2009-09-02 8:01 ` 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=m3k50i34kp.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).