+2009-08-25 Joel E. Denny <jdenny@clemson.edu>
+
+ More fixes related to last two patches.
+ * data/c.m4 (b4_table_value_equals): Comment that YYID must be
+ defined.
+ * data/glr.c, data/lalr1.cc, data/lalr1.java, data/yacc.c: Fix
+ yytable comments: zero indicates syntax error not default
+ action.
+ * data/glr.c (yyis_pact_ninf): Rename to...
+ (yypact_value_is_default): ... this.
+ (yyisDefaultedState): Update for rename.
+ (yyis_table_ninf): Rename to...
+ (yytable_value_is_error): ... this, and check for value zero
+ besides just YYTABLE_NINF.
+ (yygetLRActions): Check for default value from yypact. It
+ appears that this check is always performed before this function
+ is invoked, and so adding the check here is probably redundant.
+ However, the code may evolve after this subtlety is forgotten.
+ Also, update for rename to yytable_value_is_error. Because that
+ macro now checks for zero, a different but equivalent branch of
+ the if-then-else here is evaluated.
+ (yyreportSyntaxError): Update for rename to
+ yytable_value_is_error. The zero condition was mishandled
+ before.
+ (yyrecoverSyntaxError): Update for renames. No behavioral
+ changes.
+ * data/lalr1.cc, data/lalr1.java (yy_pact_value_is_default_):
+ New function.
+ (yy_table_value_is_error_): New function.
+ (parse): Use new functions where possible. No behavioral
+ changes.
+ (yysyntax_error_, yysyntax_error): Use yy_table_value_is_error_.
+ The zero condition was mishandled before.
+ * data/yacc.c (yyis_pact_ninf): Rename to...
+ (yypact_value_is_default): ... this.
+ (yyis_table_ninf): Rename to...
+ (yytable_value_is_error): ... this, and check for value zero
+ besides just YYTABLE_NINF.
+ (yysyntax_error): Update for rename to yytable_value_is_error.
+ The zero condition was mishandled before.
+ (yyparse): Update for renames. No behavioral changes.
+ * src/tables.h: Improve comments about yypact, yytable, etc.
+ more. Most importantly, say yytable value of zero means syntax
+ error not default action.
+
+2009-08-25 Joel E. Denny <jdenny@clemson.edu>
+
+ Fix %error-verbose for conflicts resolved by %nonassoc.
+ * NEWS (2.5): Document.
+ * data/glr.c (yyreportSyntaxError): Fix this by checking
+ yyis_table_ninf.
+ * data/yacc.c (yysyntax_error): Likewise.
+ * data/lalr1.cc (yysyntax_error_): Fix this by checking
+ yytable_ninf_.
+ * data/lalr1.java (yysyntax_error): Likewise.
+ * tests/conflicts.at (%nonassoc and eof): Update expected output
+ and remove FIXME.
+
+2009-08-25 Joel E. Denny <jdenny@clemson.edu>
+
+ Some code and documentation improvements.
+ * data/c.m4 (b4_table_value_equals): New macro to capture
+ some repeated code.
+ * data/glr.c (yyis_pact_ninf): Use it here.
+ (yyis_table_ninf): Likewise.
+ (yyreportSyntaxError): Improve internal comments.
+ * data/yacc.c (yyis_pact_ninf): New macro copied from glr.c.
+ Use it everywhere possible.
+ (yyis_table_ninf): Likewise.
+ (yysyntax_error): Improve internal comments.
+ * data/lalr1.cc (yysyntax_error_): Likewise.
+ * data/lalr1.java (yysyntax_error): Likewise.
+ * src/tables.h: Improve comments about yypact, yytable, etc.
+
+2009-08-21 Joel E. Denny <jdenny@clemson.edu>
+
+ Use locale when quoting.
+ * src/scan-gram.l (SC_ESCAPED_STRING, SC_ESCAPED_CHARACTER): Use
+ quote rather than implementing quoting here.
+
+2009-08-20 Eric Blake <ebb9@byu.net>
+
+ Make previous patch more robust.
+ * src/output.c (ARRAY_CARDINALITY): New macro, copied from
+ argmatch.h.
+ (output_skeleton): Use it.
+ Suggested by Akim Demaille.
+
+ Import latest m4/m4.m4.
+ * submodules/autoconf: Update to autoconf 2.64.
+ * configure.ac (M4_GNU_OPTION): New define.
+ * src/output.c (output_skeleton): Use it to resolve FIXME.
+ * NEWS: Mention this.
+
+2009-08-19 Joel E. Denny <jdenny@clemson.edu>
+
+ Fix complaints about escape sequences.
+ Discussed starting at
+ <http://lists.gnu.org/archive/html/bison-patches/2009-08/msg00036.html>.
+ * src/scan-gram.l (SC_ESCAPED_STRING, SC_ESCAPED_CHARACTER):
+ For a \0 and similar escape sequences meaning the null
+ character, report an invalid escape sequence instead of an
+ invalid null character because the latter does not actually
+ appear in the user's input.
+ In all escape sequence complaints, don't escape the initial
+ backslash, and don't quote when the sequence appears at the end
+ of the complaint line unless there's whitespace that quotearg
+ won't escape.
+ Consistently say "invalid" not "unrecognized".
+ Consistently prefer "empty character literal" over "extra
+ characters in character literal" warning for invalid escape
+ sequences; that is, consistently discard those sequences.
+ * tests/input.at (Bad escapes in literals): New.
+
projects / bison.git / blobdiff