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

doc: minor fixes

Browse Source 
* 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:
Akim Demaille
2015-01-15 17:26:43 +01:00
parent 88ffc4b907
commit 559b30881d
4 changed files with 1412 additions and 966 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
data/bison.m4
View File

@@ -437,7 +437,6 @@ m4_define([b4_symbol_action_location],
# b4_symbol_action(SYMBOL-NUM, KIND) # b4_symbol_action(SYMBOL-NUM, KIND)
# ---------------------------------- # ----------------------------------
# Run the action KIND (destructor or printer) for SYMBOL-NUM. # 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], m4_define([b4_symbol_action],
[b4_symbol_if([$1], [has_$2], [b4_symbol_if([$1], [has_$2],
[b4_dollar_pushdef([(*yyvaluep)], [b4_dollar_pushdef([(*yyvaluep)],

2365
doc/Doxyfile.in
View File

File diff suppressed because it is too large Load Diff

8
doc/bison.texi
View File

@@ -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 The unary-minus is another typical example where associativity is
usually over-specified, see @ref{Infix Calc, , Infix Notation 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 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 since it also defines its associativity. While this is harmless in the
traditional example, who knows how @code{NEG} might be used in future 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 in order to compute the (default) value of @code{@@$} in a reduction, the
parser basically runs parser basically runs
@example @example
@@$.begin = @@$1.begin; @@$.begin = @@1.begin;
@@$.end = @@$@var{N}.end; // The location of last right-hand side symbol. @@$.end = @@@var{N}.end; // The location of last right-hand side symbol.
@end example @end example
@noindent @noindent
so there must be copyable @code{begin} and @code{end} members; 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 @noindent
The grammar itself is straightforward (@pxref{Location Tracking Calc, , The grammar itself is straightforward (@pxref{Location Tracking Calc, ,
Location Tracking Calculator: @code{ltcalc}}). Location Tracking Calculator - @code{ltcalc}}).
@comment file: calc++-parser.yy @comment file: calc++-parser.yy
@example @example

4
src/files.h
View File

@@ -64,7 +64,9 @@ extern char *all_but_ext;
void compute_output_file_names (void); void compute_output_file_names (void);
void output_file_names_free (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...) * \param source whether this is a source file (*c, *.java...)
* as opposed to a report (*.output, *.dot...). * as opposed to a report (*.output, *.dot...).
*/ */