Future/bison
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/bison.git synced 2026-03-15 23:33:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: minor fixes to "Understanding" section

Browse Source 
* doc/bison.texinfo (Understanding): Minor wording fixes and
improvements.  Fixes problems reported in
<https://savannah.gnu.org/patch/?4306>.
(cherry picked from commit 35880c82dc)
This commit is contained in:
Paul Eggert
2012-03-17 12:52:47 -07:00
committed by Akim Demaille
parent 05061eca7c
commit d13d14ccb2
1 changed files with 10 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
doc/bison.texinfo
View File

@@ -7983,9 +7983,9 @@ exp (9)
@cindex pointed rule @cindex pointed rule
@cindex rule, pointed @cindex rule, pointed
Bison then proceeds onto the automaton itself, describing each state Bison then proceeds onto the automaton itself, describing each state
with it set of @dfn{items}, also known as @dfn{pointed rules}. Each with its set of @dfn{items}, also known as @dfn{pointed rules}. Each
item is a production rule together with a point (marked by @samp{.}) item is a production rule together with a point (@samp{.}) marking
that the input cursor. the location of the input cursor.
@example @example
state 0 state 0
@@ -8002,7 +8002,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 symbol (here, @code{exp}). When the parser returns to this state right
after having reduced a rule that produced an @code{exp}, the control 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 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 the parse stack, and the control flow jumps to state 1. Any other
lookahead triggers a syntax error.'' lookahead triggers a syntax error.''
@@ -8015,8 +8015,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 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 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 you want to see more detail you can invoke @command{bison} with
@option{--report=itemset} to list all the items, include those that can @option{--report=itemset} to list the derived items as well:
be derived:
@example @example
state 0 state 0
@@ -8068,11 +8067,11 @@ state 2
@noindent @noindent
In state 2, the automaton can only shift a symbol. For instance, In state 2, the automaton can only shift a symbol. For instance,
because of the item @samp{exp -> exp . '+' exp}, if the lookahead if because of the item @samp{exp -> exp . '+' exp}, if the lookahead is
@samp{+}, it will be shifted on the parse stack, and the automaton @samp{+} it is shifted onto the parse stack, and the automaton
control will jump to state 4, corresponding to the item @samp{exp -> exp jumps to state 4, corresponding to the item @samp{exp -> exp '+' . exp}.
'+' . exp}. Since there is no default action, any other token than Since there is no default action, any lookahead not listed triggers a syntax
those listed above will trigger a syntax error. error.
@cindex accepting state @cindex accepting state
The state 3 is named the @dfn{final state}, or the @dfn{accepting The state 3 is named the @dfn{final state}, or the @dfn{accepting