Hello, Andy Wingo <[email protected]> writes:
> On Mon 11 Jan 2010 14:38, [email protected] (Ludovic Courtès) writes: > >> Mike Gran <[email protected]> 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). We could, but it would break programs that have been assuming the ‘C’ locale, e.g., when parsing of printing data, etc... Thanks, Ludo’.
