* NEWS (2.3a+): In the %code entry, reference section `Bison

Declaration Summary' from the manual now since the %code summary has
moved there.
* doc/bison.texinfo (Prologue Alternatives): Mention that directives
in the rules section must be terminated by semicolons.

diff --git a/ChangeLog b/ChangeLog
index c0caf03ff56a52c70ec622f31e63034140b2d161..6eeb9d4f6cbf5390287d92ff33f13a2f45ea6303 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -9,6 +9,12 @@
        <http://lists.gnu.org/archive/html/help-bison/2007-05/msg00018.html>.
        * THANKS: Add Frans Englich.
 
+       * NEWS (2.3a+): In the %code entry, reference section `Bison
+       Declaration Summary' from the manual now since the %code summary has
+       moved there.
+       * doc/bison.texinfo (Prologue Alternatives): Mention that directives
+       in the rules section must be terminated by semicolons.
+
 2007-05-20  Joel E. Denny  <jdenny@ces.clemson.edu>
 
        Extend the front-end API for %define variables to more completely

diff --git a/NEWS b/NEWS
index 854023ccd5bf91df0a37ba24213b3d79ca231efc..e5ff7976ef69fb3946e0d0cf10e49359e96e57d0 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -51,8 +51,8 @@ Changes in version 2.3a+ (????-??-??):
     3. `%code provides {CODE}' replaces `%end-header    {CODE}'
     4. `%code top      {CODE}' replaces `%before-header {CODE}'
 
-  See the %code entries in `Appendix A Bison Symbols' in the Bison manual for a
-  summary of the new functionality.  See the new section `Prologue
+  See the %code entries in section `Bison Declaration Summary' in the Bison
+  manual for a summary of the new functionality.  See the new section `Prologue
   Alternatives' for a detailed discussion including the advantages of %code
   over the traditional Yacc prologues.
 

diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index c344ec73d5fb5aa13da3db5322a5e366f4f41526..55a7759a2355080cdd2b8a03904587beb12cb4f0 100644 (file)
--- a/doc/bison.texinfo
+++ b/doc/bison.texinfo
@@ -2956,6 +2956,8 @@ type:
 You could even place each of the above directive groups in the rules section of
 the grammar file next to the set of rules that uses the associated semantic
 type.
+(In the rules section, you must terminate each of those directives with a
+semicolon.)
 And you don't have to worry that some directive (like a @code{%union}) in the
 definitions section is going to adversely affect their functionality in some
 counter-intuitive manner just because it comes first.