mirror of
https://git.savannah.gnu.org/git/bison.git
synced 2026-03-09 04:13:03 +00:00
doc: minor fixes
* doc/bison.texi: Fix warnings about colon in reference names. * data/bison.m4, src/files.h: Fix comments. * doc/Doxyfile.in: update.
This commit is contained in:
@@ -437,7 +437,6 @@ m4_define([b4_symbol_action_location],
|
||||
# b4_symbol_action(SYMBOL-NUM, KIND)
|
||||
# ----------------------------------
|
||||
# Run the action KIND (destructor or printer) for SYMBOL-NUM.
|
||||
# Same as in C, but using references instead of pointers.
|
||||
m4_define([b4_symbol_action],
|
||||
[b4_symbol_if([$1], [has_$2],
|
||||
[b4_dollar_pushdef([(*yyvaluep)],
|
||||
|
||||
2365
doc/Doxyfile.in
2365
doc/Doxyfile.in
File diff suppressed because it is too large
Load Diff
@@ -7550,7 +7550,7 @@ in an associativity related conflict, which can be specified as follows.
|
||||
|
||||
The unary-minus is another typical example where associativity is
|
||||
usually over-specified, see @ref{Infix Calc, , Infix Notation
|
||||
Calculator: @code{calc}}. The @code{%left} directive is traditionally
|
||||
Calculator - @code{calc}}. The @code{%left} directive is traditionally
|
||||
used to declare the precedence of @code{NEG}, which is more than needed
|
||||
since it also defines its associativity. While this is harmless in the
|
||||
traditional example, who knows how @code{NEG} might be used in future
|
||||
@@ -10748,8 +10748,8 @@ it must be copyable;
|
||||
in order to compute the (default) value of @code{@@$} in a reduction, the
|
||||
parser basically runs
|
||||
@example
|
||||
@@$.begin = @@$1.begin;
|
||||
@@$.end = @@$@var{N}.end; // The location of last right-hand side symbol.
|
||||
@@$.begin = @@1.begin;
|
||||
@@$.end = @@@var{N}.end; // The location of last right-hand side symbol.
|
||||
@end example
|
||||
@noindent
|
||||
so there must be copyable @code{begin} and @code{end} members;
|
||||
@@ -11337,7 +11337,7 @@ regular destructors. All the values are printed using their
|
||||
|
||||
@noindent
|
||||
The grammar itself is straightforward (@pxref{Location Tracking Calc, ,
|
||||
Location Tracking Calculator: @code{ltcalc}}).
|
||||
Location Tracking Calculator - @code{ltcalc}}).
|
||||
|
||||
@comment file: calc++-parser.yy
|
||||
@example
|
||||
|
||||
@@ -64,7 +64,9 @@ extern char *all_but_ext;
|
||||
void compute_output_file_names (void);
|
||||
void output_file_names_free (void);
|
||||
|
||||
/** Record that we generate file \a file_name.
|
||||
/** Record that we generate a file.
|
||||
*
|
||||
* \param file_name the name of file being generated.
|
||||
* \param source whether this is a source file (*c, *.java...)
|
||||
* as opposed to a report (*.output, *.dot...).
|
||||
*/
|
||||
|
||||
Reference in New Issue
Block a user