* doc/bison.texinfo: Correct typos in previous fix.

[bison.git] / doc / bison.texinfo

diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index c1b04946e6810916b1d7edfebabe774f30fd2f0a..8babb6f8f9cb9855083c0c2a890249ba3e5de715 100644 (file)
--- a/doc/bison.texinfo
+++ b/doc/bison.texinfo
@@ -3779,10 +3779,11 @@ Declare that the @var{code} must be invoked before parsing each time
 For instance, if your locations use a file name, you may use
 
 @example
-%parse-param @{ const char *file @};
+%parse-param @{ char const *file_name @};
 %initial-action
 @{
-  @@$.begin.file = @@$.end.file = file;
+  @@$.begin.file_name = @@$.end.file_name = file_name;
+  @@$.begin.file_name = @@$.end.file_name = file_name;
 @};
 @end example
 
@@ -6950,7 +6951,7 @@ Symbols}.
 @c - %locations
 @c - class Position
 @c - class Location
-@c - %define "file_type" "const symbol::Symbol"
+@c - %define "file_name_type" "const symbol::Symbol"
 
 When the directive @code{%locations} is used, the C++ parser supports
 location tracking, see @ref{Locations, , Locations Overview}.  Two
@@ -6962,7 +6963,7 @@ and a @code{location}, a range composed of a pair of
 The name of the file.  It will always be handled as a pointer, the
 parser will never duplicate nor deallocate it.  As an experimental
 feature you may change it to @samp{@var{type}*} using @samp{%define
-"file_type" "@var{type}"}.
+"file_name_type" "@var{type}"}.
 @end deftypemethod
 
 @deftypemethod {position} {unsigned int} line
@@ -7322,7 +7323,7 @@ automatically propagated.
 %initial-action
 @{
   // Initialize the initial location.
-  @@$.begin.file = @@$.end.file = &driver.file;
+  @@$.begin.file_name = @@$.end.file_name = &driver.file;
 @};
 @end example