Token value in custom error reporting

Daniele Nicolodi <[email protected]>
Newsgroups gmane.comp.parsers.bison.general
Message-ID <[email protected]>
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.