Hello,
I am working on a project that uses Bison to generate a parser and Meson
as build system. I would like to include Bison as a subproject [1] in
particular to make it easier for folks to hack on the project on OSes
where managing dependencies is not easy (ie Windows). For this, I would
need t
On 20/12/2020 08:09, Akim Demaille wrote:
> Hi Daniele,
>
>> Le 19 déc. 2020 à 20:17, Daniele Nicolodi a écrit :
>>
>> Hello,
>>
>> I am working on a project that uses Bison to generate a parser and Meson
>> as build system. I would like to include Bis
On 20/12/2020 15:31, Christian Schoenebeck via Users list for the GNU
Bison parser generator wrote:
> On Sonntag, 20. Dezember 2020 12:33:45 CET Daniele Nicolodi wrote:
>> On 20/12/2020 08:09, Akim Demaille wrote:
>>> Hi Daniele,
>>>
>>>> Le 19 déc.
Hello,
error reporting has always been a pain point for me in the use of flex
and bison, especially in coordinated error handling between the scanner
and the grammar. I am very happy to see a lot of improvements in this
area in the 3.6 release!
Trying to use `%define parse.error custom` in a proj
Hello,
error reporting has always been a pain point for me in the use of flex
and bison, especially in coordinated error handling between the scanner
and the grammar. I am very happy to see a lot of improvements in this
area in the 3.6 release!
Trying to use `%define parse.error custom` in a proj
Hi Akim,
On 17/06/2020 23:43, Akim Demaille wrote:
> I think it's a mistake to try to use the semantic value in error messages.
The goal would not be to use the semantic value in the error message,
but to use additional context attached to the token by the lexer to
decide how to report the error.
Hello,
in Bison 3.6 is it possible to redefine the literal string associated to
the YYerror symbol (and to the YYEOF, YYUNDEF ones, although I don't
have immediate need for this)?
Doing it in the naive way:
%token YYerror "ERROR"
results in a warning:
warning: symbol YYerror given more than on
On 18/06/2020 00:39, Akim Demaille wrote:
>
>
>> Le 18 juin 2020 à 07:49, Daniele Nicolodi a écrit :
>>
>> Hi Akim,
>>
>> On 17/06/2020 23:43, Akim Demaille wrote:
>>> I think it's a mistake to try to use the semantic value in error message
On 18/06/2020 00:44, Akim Demaille wrote:
> There is no way to rename it, and it wouldn't make sense as the error
> token is never presented as an "expected token". The error token never
> shows to the (end) user. It appears in the debug traces, but that's
> for the developer.
What about YYEOF a
On 19/06/2020 00:13, Akim Demaille wrote:
> Hi Daniele,
>
>> Le 18 juin 2020 à 19:20, Akim Demaille a écrit :
>>
>>> However I have a ton of tests that expect the lexer to emit a
>>> "LEX_ERROR" token on error and I am considering to use YYerror special
>>> token to report errors instead. Thus th
Hello,
the historical pairing is using Flex with Bison. However, while Bison is
under active development and seems to be a very solid code base, there
isn't much activity on the Flex side https://github.com/westes/flex and
Flex codebase and capabilities show their age.
I recently became aware of
On 08/07/2020 15:30, Christian Schoenebeck wrote:
> On Mittwoch, 8. Juli 2020 22:14:23 CEST Akim Demaille wrote:
>>> So yes, you could certainly address this to work correctly with Flex with
>>> additional measures,
>>
>> The case you are citing above is straightforward to handle the same
>> way I
12 matches
Mail list logo
