[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Parse inline scheme using per-expression port (issue 557330043 by ad
|
From: |
Han-Wen Nienhuys |
|
Subject: |
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden) |
|
Date: |
Mon, 10 Feb 2020 08:27:18 +0100 |
On Sun, Feb 9, 2020 at 7:00 PM <address@hidden> wrote:
>
> Now my original solution was aimed at staying in binary even during
> Scheme times while Antonio Ospite does go all-in on UTF-8 in Scheme. So
> the result of combining my and his work is a chimæra which I am less
> confident about than my own code on its own. Being in binary mode for
> Flex means that we can deal robustly with code that is not properly in
> UTF-8. For example, we had input files that were ASCII-only except for
> some comments containing latters in the Latin-1 plane. In binary mode,
> our lexer deals gracefully with such abominations while Guile balks at
> such files when doing UTF-8 processing.
>
The reason we've been doing it this way, is that Gary gave us this code in
1999, when we didn't know anything about encodings, ports or Scheme, and it
worked.
However, there is no good reason why we should have port for the entire
file. If you have a .ly file that doesn't have a single # , then there is
no reason to have a port at all.
--
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), dak, 2020/02/07
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), hanwenn, 2020/02/09
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), dak, 2020/02/09
- Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden),
Han-Wen Nienhuys <=
- Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), Han-Wen Nienhuys, 2020/02/10
- Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), Han-Wen Nienhuys, 2020/02/10
- Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), David Kastrup, 2020/02/10
- Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), Han-Wen Nienhuys, 2020/02/10
- Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), David Kastrup, 2020/02/10
- Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), Han-Wen Nienhuys, 2020/02/11
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), David Kastrup, 2020/02/10
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), hanwenn, 2020/02/11
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), lemzwerg, 2020/02/13