From 351e3630bbf759e18adf756c54abc89275805111 Mon Sep 17 00:00:00 2001 From: Akim Demaille Date: Tue, 6 Nov 2018 08:39:14 +0100 Subject: [PATCH] NEWS: update --- NEWS | 4 ++++ TODO | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/NEWS b/NEWS index db8bed74..219b4b4a 100644 --- a/NEWS +++ b/NEWS @@ -2,6 +2,10 @@ GNU Bison NEWS * Noteworthy changes in release ?.? (????-??-??) [?] +** Bug fixes + + Several portability issues have been fixed in the build system, in the + test suite, and in the generated parsers in C++. * Noteworthy changes in release 3.2 (2018-10-29) [stable] diff --git a/TODO b/TODO index fabf6c25..0c89934e 100644 --- a/TODO +++ b/TODO @@ -220,6 +220,10 @@ The users are not provided with enough tools to forge their error messages. See for instance "Is there an option to change the message produced by YYERROR_VERBOSE?" by Simon Sobisch, on bison-help. +See also +https://www.cs.tufts.edu/~nr/cs257/archive/clinton-jefferey/lr-error-messages.pdf +and https://research.swtch.com/yyerror. + ** %include This is a popular demand. We already made many changes in the parser that should make this reasonably easy to implement.