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

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

View File

@@ -1,3 +1,10 @@
2007-03-10 Joel E. Denny <jdenny@ces.clemson.edu>
* doc/bison.texinfo (Destructor Decl): Fix typo reported by Sebastian
Setzer.
(Java Differences): Fix some typos.
* THANKS: Add Sebastian Setzer.
2007-03-07 Paolo Bonzini <bonzini@gnu.org> 2007-03-07 Paolo Bonzini <bonzini@gnu.org>
* data/java.m4 (b4_single_class_if): Remove. * data/java.m4 (b4_single_class_if): Remove.

1
THANKS
View File

@@ -71,6 +71,7 @@ Richard Stallman rms@gnu.org
Robert Anisko anisko_r@epita.fr Robert Anisko anisko_r@epita.fr
Satya Kiran Popuri satyakiran@gmail.com Satya Kiran Popuri satyakiran@gmail.com
Sébastien Fricker sebastien.fricker@gmail.com Sébastien Fricker sebastien.fricker@gmail.com
Sebastian Setzer sebastian.setzer.ext@siemens.com
Shura debil_urod@ngs.ru Shura debil_urod@ngs.ru
Steve Murphy murf@parsetree.com Steve Murphy murf@parsetree.com
Tim Josling tej@melbpc.org.au Tim Josling tej@melbpc.org.au

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 @code{YYABORT} or @code{YYACCEPT}, or failed error recovery, or memory
exhaustion. 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 error via @code{YYERROR} are not discarded automatically. As a rule
of thumb, destructors are invoked only when user actions cannot manage of thumb, destructors are invoked only when user actions cannot manage
the memory. 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 The different structure of the Java language forces several differences
between C/C++ grammars, and grammars designed for Java parsers. This between C/C++ grammars, and grammars designed for Java parsers. This
section summarizes this differences. section summarizes these differences.
@itemize @itemize
@item @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 scanner. If there is no such block, the scanner can be any class
that implements the appropriate interface (see @pxref{Java Scanner that implements the appropriate interface (see @pxref{Java Scanner
Interface}). Interface}).
@end item @end table
Other @code{%code} blocks are not supported in Java parsers. Other @code{%code} blocks are not supported in Java parsers.
The epilogue has the same meaning as in C/C++ code and it can The epilogue has the same meaning as in C/C++ code and it can