[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

minor documentation fixes

From: Joel E. Denny
Subject: minor documentation fixes
Date: Sat, 26 May 2007 16:08:34 -0400 (EDT)

I committed this.

Index: ChangeLog
RCS file: /sources/bison/bison/ChangeLog,v
retrieving revision 1.1701
diff -p -u -r1.1701 ChangeLog
--- ChangeLog   26 May 2007 19:10:43 -0000      1.1701
+++ ChangeLog   26 May 2007 20:02:15 -0000
@@ -9,6 +9,12 @@
        * 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  <address@hidden>
        Extend the front-end API for %define variables to more completely
Index: NEWS
RCS file: /sources/bison/bison/NEWS,v
retrieving revision 1.174
diff -p -u -r1.174 NEWS
--- NEWS        8 May 2007 05:03:53 -0000       1.174
+++ NEWS        26 May 2007 20:02:15 -0000
@@ -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.
Index: doc/bison.texinfo
RCS file: /sources/bison/bison/doc/bison.texinfo,v
retrieving revision 1.231
diff -p -u -r1.231 bison.texinfo
--- doc/bison.texinfo   10 Mar 2007 21:05:24 -0000      1.231
+++ doc/bison.texinfo   26 May 2007 20:02:18 -0000
@@ -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
+(In the rules section, you must terminate each of those directives with a
 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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]