> Le 23 janv. 2020 à 08:50, Akim Demaille <[email protected]> a écrit :
>
> This series of patches plays with parse.error=detailed in bison
> itself, and then with parse.error=custom. This was an opportunity to
> change bison's syntax errors themselves, so we're going from:
>
> foo.y:1.8-13: error: syntax error, unexpected %token, expecting character
> literal or identifier or <tag>
>
> to
>
> foo.y:1.8-13: error: expected character literal or identifier or <tag>
> before %token
>
> where the expected tokens ("character literal", "identifier" and
> "<tag>") are displayed in green by default, and the unexpected one
> ("%token") is in red. I'm not sure yet of these choices, comments are
> most welcome.
No comments?
Pushed.
