+2009-09-12 Alex Rozenman <rozenman@gmail.com>
+
+ Provide an additional sub-message for clarity.
+ Add "symbol not found in production" error message when
+ an "invalid reference" is detected in named references
+ resolution.
+ * src/scan-code.l: Update "invalid reference" case.
+ * tests/named-ref.at: Adjust test-cases.
+
+2009-09-10 Joel E. Denny <jdenny@clemson.edu>
+
+ Clean up yacc.c a little.
+ * data/yacc.c: Clean up M4 for readability, and make output
+ whitespace more consistent. For the main parse function
+ comment, instead of saying "yyparse or yypush_parse", say either
+ "yyparse" or "yypush_parse" depending on which it actually is.
+
+2009-09-10 Joel E. Denny <jdenny@clemson.edu>
+
+ Fix --enable-gcc-warnings.
+ * src/parse-gram.y (%printer <param>): Handle param_none.
+
+2009-09-09 Akim Demaille <demaille@gostai.com>
+
+ lalr1.cc: syntax_error as exceptions.
+ It is common to use sort of factories in the user actions. These
+ factories may check some "syntactic" constraints that are not
+ enforced by the grammar itself. This is possible using YYERROR
+ within the action itself. Provide the user with a means to throw
+ a syntax_error exception.
+
+ * data/c++.m4 (b4_public_types_declare, b4_public_types_define):
+ Declare and define yy::parser::syntax_error.
+ * data/lalr1.cc: Include stdexcept.
+ (yy::parser::parse): Wrap the user action within a try/catch.
+ * data/glr.cc: Include stdexcept.
+