[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Token value in custom error reporting
From: |
Daniele Nicolodi |
Subject: |
Token value in custom error reporting |
Date: |
Wed, 17 Jun 2020 15:20:21 -0600 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 |
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 project I realized that
it would be very handy to have the value of the token that caused the
syntax error available in yyreport_syntax_error. Is there a way to get
to it?
Thank you!
Cheers,
Dan
- Re: Token value in custom error reporting, (continued)
- Re: Token value in custom error reporting, Hans Åberg, 2020/06/18
- Re: Token value in custom error reporting, Akim Demaille, 2020/06/18
- Re: Token value in custom error reporting, Hans Åberg, 2020/06/18
- Re: Token value in custom error reporting, Akim Demaille, 2020/06/18
- Re: Token value in custom error reporting, Hans Åberg, 2020/06/18
- Re: Token value in custom error reporting, Akim Demaille, 2020/06/19
- Re: Token value in custom error reporting, Hans Åberg, 2020/06/19
- Re: Token value in custom error reporting, Akim Demaille, 2020/06/18
Token value in custom error reporting,
Daniele Nicolodi <=