[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Error UTF-8 strings
From: |
Hans Åberg |
Subject: |
Re: Error UTF-8 strings |
Date: |
Sun, 21 Jun 2020 14:25:35 +0200 |
> On 21 Jun 2020, at 11:45, Akim Demaille <akim@lrde.epita.fr> wrote:
>
> Hi Hans,
Hello,
>> Le 21 juin 2020 à 10:19, Hans Åberg <haberg-1@telia.com> a écrit :
>>
>> Use
>> %token <name> "<string>"
>> where <string> has non-ASCII characters (high bit set), and trigger it in a
>> syntax error, as the failing token or one of the expected ones.
>
> I need details. What skeleton?
%skeleton "lalr1.cc"
> What options for parse.error?
%define parse.error verbose
> What locale are you using?
LC_CTYPE=UTF-8
> If you want some support, give us something we can actually work on.
>
> Give me something reproducible. I'll disregard anything else.
It is embedded in a grammar about the size of C++98, so it will take some time
to figure out a smaller example.
- Error UTF-8 strings, Hans Åberg, 2020/06/20
- Re: Error UTF-8 strings, Akim Demaille, 2020/06/21
- Re: Error UTF-8 strings, Hans Åberg, 2020/06/21
- Re: Error UTF-8 strings, Akim Demaille, 2020/06/21
- Re: Error UTF-8 strings,
Hans Åberg <=
- Re: Error UTF-8 strings, Hans Åberg, 2020/06/21
- Re: Error UTF-8 strings, Akim Demaille, 2020/06/22
- Re: Error UTF-8 strings, Hans Åberg, 2020/06/22
- Re: Error UTF-8 strings, Akim Demaille, 2020/06/23
- Re: Error UTF-8 strings, Hans Åberg, 2020/06/23
- Re: Error UTF-8 strings, Hans Åberg, 2020/06/23
- Re: Error UTF-8 strings, Akim Demaille, 2020/06/24
- Re: Error UTF-8 strings, Hans Åberg, 2020/06/24
- Re: Error UTF-8 strings, Hans Åberg, 2020/06/23
- Re: Error UTF-8 strings, Akim Demaille, 2020/06/24