Re: Error UTF-8 strings

> On 23 Jun 2020, at 07:47, Akim Demaille <[email protected]> wrote:
> 
>> The question is if that helps, as it is the yytname_ that is translated according to the LC_CTYPE environment variable.
>> 
>> This also introduces a locale dependency in the Bison compilation, so that the generated parser no longer is platform independent.
> 
> Yes, that is indeed exactly what I meant: verbose is bad, and always was.
> Use "detailed" instead.

This is worse, I get (in Bison 3.6.3):
error: use of undeclared identifier 'yytname_'; did you mean 'yytable_'?
          + yytnamerr_(yytname_[x0->first - 255]) + ".");

>>> So, there is no new bug in 3.6 here, just something that is well known for
>>> ages, about which you and I already discussed.
>> 
>> Yes, there is, translation dependent on LC_CTYPE, which was not before.
> 
> I believe you are mistaken, and you won't find any difference between 3.6
> and 3.5 on this regard.
> 
> To prove me wrong, give me a reproducible example.

It was in an earlier 3.x version it worked. I do not try out error reporting that often.