Thanks, I fixed up all those old patch reports in Savannah, installing the attached patch to fix the documentation, so now there's just one proposed patch left, awaiting info <https://savannah.gnu.org/patch/?4474>.
There are also some non-patch reports pending at <https://savannah.gnu.org/support/?group=bison> but I left those alone. Maybe we should switch to debbugs? It's more commonly used these days, at least among projects I help maintain.
From e1c48c9eeef94daf2a60f04f5890875a1494ea33 Mon Sep 17 00:00:00 2001 From: Paul Eggert <[email protected]> Date: Sat, 17 Mar 2012 12:52:47 -0700 Subject: [PATCH] doc: minor fixes to "Understanding" section * doc/bison.texinfo (Understanding): Minor wording fixes and improvements. Fixes problems reported in <https://savannah.gnu.org/patch/?4306>. --- doc/bison.texinfo | 21 ++++++++++----------- 1 files changed, 10 insertions(+), 11 deletions(-) diff --git a/doc/bison.texinfo b/doc/bison.texinfo index d24d0c6..2b5b314 100644 --- a/doc/bison.texinfo +++ b/doc/bison.texinfo @@ -8326,9 +8326,9 @@ exp (9) @cindex pointed rule @cindex rule, pointed Bison then proceeds onto the automaton itself, describing each state -with it set of @dfn{items}, also known as @dfn{pointed rules}. Each -item is a production rule together with a point (marked by @samp{.}) -that the input cursor. +with its set of @dfn{items}, also known as @dfn{pointed rules}. Each +item is a production rule together with a point (@samp{.}) marking +the location of the input cursor. @example state 0 @@ -8345,7 +8345,7 @@ beginning of the parsing, in the initial rule, right before the start symbol (here, @code{exp}). When the parser returns to this state right after having reduced a rule that produced an @code{exp}, the control flow jumps to state 2. If there is no such transition on a nonterminal -symbol, and the lookahead is a @code{NUM}, then this token is shifted on +symbol, and the lookahead is a @code{NUM}, then this token is shifted onto the parse stack, and the control flow jumps to state 1. Any other lookahead triggers a syntax error.'' @@ -8358,8 +8358,7 @@ report lists @code{NUM} as a lookahead token because @code{NUM} can be at the beginning of any rule deriving an @code{exp}. By default Bison reports the so-called @dfn{core} or @dfn{kernel} of the item set, but if you want to see more detail you can invoke @command{bison} with -@option{--report=itemset} to list all the items, include those that can -be derived: +@option{--report=itemset} to list the derived items as well: @example state 0 @@ -8411,11 +8410,11 @@ state 2 @noindent In state 2, the automaton can only shift a symbol. For instance, -because of the item @samp{exp -> exp . '+' exp}, if the lookahead if -@samp{+}, it will be shifted on the parse stack, and the automaton -control will jump to state 4, corresponding to the item @samp{exp -> exp -'+' . exp}. Since there is no default action, any other token than -those listed above will trigger a syntax error. +because of the item @samp{exp -> exp . '+' exp}, if the lookahead is +@samp{+} it is shifted onto the parse stack, and the automaton +jumps to state 4, corresponding to the item @samp{exp -> exp '+' . exp}. +Since there is no default action, any lookahead not listed triggers a syntax +error. @cindex accepting state The state 3 is named the @dfn{final state}, or the @dfn{accepting -- 1.7.6.5
