[Top][All Lists]

[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: Tue, 23 Jun 2020 11:12:22 +0200

> On 23 Jun 2020, at 07:47, Akim Demaille <akim@lrde.epita.fr> 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.

From what I can see by comparing the outputs, UTF-8 is still converted, though 
the writeout might be correct. With "verbose", I get in yytname_ an entry
whereas with "detailed" in yy_sname

An improvement if you are not supposed to read the parser source code.

The other errors occurred because I report errors in the grammar actions as:
        throw syntax_error(@x, "Name " + $x.text + " already defined in this 
scope as "
          + yytnamerr_(yytname_[x0->first - 255]) + ".");

So perhaps you made some API for that?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]