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

* doc/bison.texinfo (Destructor Decl): Fix typo reported by Sebastian

Browse Source 
Setzer.
(Java Differences): Fix some typos.
* THANKS: Add Sebastian Setzer.
This commit is contained in:
Joel E. Denny
2007-03-10 21:05:24 +00:00
parent 01b477c6b6
commit 2955354793
3 changed files with 11 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/bison.texinfo
View File

@@ -4396,7 +4396,7 @@ The parser can @dfn{return immediately} because of an explicit call to
@code{YYABORT} or @code{YYACCEPT}, or failed error recovery, or memory
exhaustion.
Right-hand size symbols of a rule that explicitly triggers a syntax
Right-hand side symbols of a rule that explicitly triggers a syntax
error via @code{YYERROR} are not discarded automatically. As a rule
of thumb, destructors are invoked only when user actions cannot manage
the memory.
@@ -8617,7 +8617,7 @@ The field's type can be changed using @samp{%define "stype"
The different structure of the Java language forces several differences
between C/C++ grammars, and grammars designed for Java parsers. This
section summarizes this differences.
section summarizes these differences.
@itemize
@item
@@ -8650,7 +8650,7 @@ blocks, if specified, should include the implementation of the
scanner. If there is no such block, the scanner can be any class
that implements the appropriate interface (see @pxref{Java Scanner
Interface}).
@end item
@end table
Other @code{%code} blocks are not supported in Java parsers.
The epilogue has the same meaning as in C/C++ code and it can