Hello,
Andy Wingo wi...@pobox.com writes:
This is complicated in Guile by #!. A reasonable thing would be to have
the reader have a bit on whether it actually saw an expression yet or
not. If not, ^;+ [^\n]*coding: ... would set the file's encoding.
I think it would make sense to follow
Hi,
On Thu 28 May 2009 16:37, l...@gnu.org (Ludovic Courtès) writes:
Andy Wingo wi...@pobox.com writes:
This is complicated in Guile by #!. A reasonable thing would be to have
the reader have a bit on whether it actually saw an expression yet or
not. If not, ^;+ [^\n]*coding: ... would set
Hello,
Mike Gran spk...@yahoo.com writes:
This all means that grepping the coding is a true preprocessing
step, divorced from the reader.
Not necessarily. The encoding can be stored in a fluid, or associated
with the current input port, and modified by `scm_read ()' as it
encounters encoding
On Tue 26 May 2009 00:22, l...@gnu.org (Ludovic Courtès) writes:
However, this relies on eval-after-read semantics. That is, if the
whole file is read at once, *then* evaluated, that won't work, right?
Or read at once, *then* compiled, *then* evaluated; or even, read one
expression at a time,
From: Andy Wingo wi...@pobox.com
On Tue 26 May 2009 00:22, l...@gnu.org (Ludovic Courtès) writes:
However, this relies on eval-after-read semantics. That is, if the
whole file is read at once, *then* evaluated, that won't work, right?
Or read at once, *then* compiled, *then*
Hello,
Michael Gran spk...@yahoo.com writes:
add tests for encoding/decoding wide strings
Nice!
Just a bit of cosmetic nitpicking:
* test-suite/tests/encoding_utf8.test: new
Please use hyphens instead of underscores in file names, for
consistency.
+(setlocale LC_ALL en_US.utf8)
On Tue, 2009-05-26 at 00:22 +0200, Ludovic Courtès wrote:
Hello,
Just a bit of cosmetic nitpicking:
* test-suite/tests/encoding_utf8.test: new
Please use hyphens instead of underscores in file names, for
consistency.
OK
+(setlocale LC_ALL en_US.utf8)
[...]
