doc: clean up references to `Locations Overview'.

* doc/bison.texinfo (Locations Overview): Rename node to...
(Locations): ... this, which is its section name.  Update menus to
match that and not to use the title `Tracking Locations', which is
a different section.
This commit is contained in:
Joel E. Denny
2011-05-29 22:30:55 -04:00
parent 7404cdf3a1
commit 8348436580
2 changed files with 11 additions and 3 deletions

View File

@@ -1,3 +1,11 @@
2011-05-29 Joel E. Denny <joeldenny@joeldenny.org>
doc: clean up references to `Locations Overview'.
* doc/bison.texinfo (Locations Overview): Rename node to...
(Locations): ... this, which is its section name. Update menus to
match that and not to use the title `Tracking Locations', which is
a different section.
2011-05-29 Joel E. Denny <joeldenny@joeldenny.org>
doc: clean up references to `Tracking Locations'.

View File

@@ -125,7 +125,7 @@ The Concepts of Bison
the name of an identifier, etc.).
* Semantic Actions:: Each rule can have an action containing C code.
* GLR Parsers:: Writing parsers for general context-free languages.
* Locations Overview:: Tracking Locations.
* Locations:: Overview of location tracking.
* Bison Parser:: What are Bison's input and output,
how is the output used?
* Stages:: Stages in writing and running Bison grammars.
@@ -449,7 +449,7 @@ use Bison or Yacc, we suggest you start by reading this chapter carefully.
the name of an identifier, etc.).
* Semantic Actions:: Each rule can have an action containing C code.
* GLR Parsers:: Writing parsers for general context-free languages.
* Locations Overview:: Tracking Locations.
* Locations:: Overview of location tracking.
* Bison Parser:: What are Bison's input and output,
how is the output used?
* Stages:: Stages in writing and running Bison grammars.
@@ -1205,7 +1205,7 @@ will suffice. Otherwise, we suggest
%@}
@end example
@node Locations Overview
@node Locations
@section Locations
@cindex location
@cindex textual location