[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: |
Tue, 11 Feb 2020 09:44:43 +0100 |
On Mon, Feb 10, 2020 at 11:21 PM David Kastrup <address@hidden> wrote:
>
> Or maybe the file offset got advanced because Guile peeked ahead in
> order to check whether there is an UTF-8 signature? I forget what they
> are called, basically zero-space characters. Byte order mark? I am not
> saying that it is that, but I remember that Guile could do some pretty
> funky things at opening even something like a string port.
>
More mundane. Source_file::get_counts returns a byte_offset, but that is
not a global but per-line offset.
PTAL
--
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen
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
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), jonas . hahnfeld, 2020/02/13
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), hanwenn, 2020/02/13
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), jonas . hahnfeld, 2020/02/13
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), hanwenn, 2020/02/19
Re: Parse inline scheme using per-expression port (issue 557330043 by address@hidden), hanwenn, 2020/02/26