From: Mike Gran <spk121@yahoo.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel@gnu.org
Subject: Re: Sting abstraction 2
Date: Wed, 20 May 2009 20:33:25 -0700 [thread overview]
Message-ID: <1242876805.32575.8005.camel@localhost.localdomain> (raw)
In-Reply-To: <87hbzfmjtv.fsf@gnu.org>
On Thu, 2009-05-21 at 01:32 +0200, Ludovic Courtès wrote:
> > (Did I ever mention this backtrace tree
> > pic? http://www.lonelycactus.com/uploaded_images/test[1]-765536.PNG
> > It shows that for all the scripts the test suite, all of the calls to
> > low-level read and write pass through those two functions.)
>
> Nice. I suppose you had breakpoints in GDB, captured the output of
> "bt", frobbed it and fed it to `dot'?
>
Pretty much.
> > I have changed my opinion on one issue. I don't believe that Guile
> > ports should have a specific encoding: they should just use the
> > locale. This is just pragmatism. Guile ports and the default reader
> > are annoying things to hack. I am loathe to touch them more than is
> > necessary.
> >
> > The R6RS ports have the nice transcoder idea. It might be more fun to
> > push port-specific encodings to that library.
>
> Are you saying that we'd have an implementation of the R6 port API that
> DTRT, whereas Guile's current API would remain encoding-oblivious?
>
I am thinking that the setlocale character encoding becomes the encoding
for all legacy Guile port IO, and if you want to operate on a port that
has a different locale than your setlocale character encoding, you need
to do that through an R6RS port.
> Thanks!
>
> Ludo'.
-Mike
next prev parent reply other threads:[~2009-05-21 3:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 15:24 Sting abstraction 2 Mike Gran
2009-05-20 21:11 ` 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 [this message]
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=1242876805.32575.8005.camel@localhost.localdomain \
--to=spk121@yahoo.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).