From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: bug-guile@gnu.org, guile-devel@gnu.org
Subject: Re: UTF-8 regression in guile 1.9.5
Date: Mon, 11 Jan 2010 22:18:14 +0100 [thread overview]
Message-ID: <m36378pch5.fsf@pobox.com> (raw)
In-Reply-To: <87ocl0bw3m.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 11 Jan 2010 14:38:05 +0100")
On Mon 11 Jan 2010 14:38, ludo@gnu.org (Ludovic Courtès) writes:
> Mike Gran <spk121@yahoo.com> writes:
>
>> But as far as the greater question of the side effects of setting locale
>> early on startup... The parsing of any source code files after locale
>> is set will be done in that context. I don't think it would do anything
>> unexpected. The reader and the port routines tend to do their own parsing,
>> and don't tend to rely on libc locale-specific routines. Even so, it
>> would take some auditing to prove that there would be no effect.
>
> Source files should have the right ‘coding:’ meta anyway. I just
> changed the compiler to install the current user locale [0], as that’s
> typically what a standalone program does.
If we're taking this tack, perhaps we should setlocale in the `guile'
binary (but not by default when used by a library).
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-01-11 21:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 18:43 UTF-8 regression in guile 1.9.5 Linas Vepstas
2009-12-06 19:16 ` Mike Gran
2009-12-06 19:33 ` Linas Vepstas
2009-12-06 20:40 ` Mike Gran
2009-12-06 20:43 ` Linas Vepstas
2009-12-11 10:29 ` Andy Wingo
2009-12-11 15:05 ` Mike Gran
2009-12-11 15:40 ` Linas Vepstas
2009-12-11 22:50 ` Ludovic Courtès
2010-01-09 18:07 ` Andy Wingo
2010-01-10 22:00 ` Mike Gran
2010-01-11 13:38 ` Ludovic Courtès
2010-01-11 21:18 ` Andy Wingo [this message]
2010-01-12 11:25 ` Ludovic Courtès
2010-01-12 19:36 ` Andy Wingo
2010-01-12 22:26 ` 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=m36378pch5.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--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).