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

style: doc: remove useless reference to 'int' in integral types

Browse Source 
* doc/bison.texi: Prefer 'unsigned' to 'unsigned int'.  Likewise for
long and short.
This commit is contained in:
Akim Demaille
2018-08-12 15:00:35 +02:00
parent 9df53e7288
commit c226d4ed48
2 changed files with 7 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
TODO
View File

@@ -112,7 +112,7 @@ We could (should?) also treat the case of the undef_token, which is
numbered 257 for yylex, and 2 internal. Both appear for instance in numbered 257 for yylex, and 2 internal. Both appear for instance in
toknum: toknum:
const unsigned short int const unsigned short
parser::yytoken_number_[] = parser::yytoken_number_[] =
{ {
0, 256, 257, 258, 259, 260, 261, 262, 263, 264, 0, 256, 257, 258, 259, 260, 261, 262, 263, 264,

12
doc/bison.texi
View File

@@ -2883,7 +2883,7 @@ can be done with two @var{Prologue} blocks, one before and one after the
@group @group
%union @{ %union @{
long int n; long n;
tree t; /* @r{@code{tree} is defined in @file{ptypes.h}.} */ tree t; /* @r{@code{tree} is defined in @file{ptypes.h}.} */
@} @}
@end group @end group
@@ -2935,7 +2935,7 @@ Look again at the example of the previous section:
@group @group
%union @{ %union @{
long int n; long n;
tree t; /* @r{@code{tree} is defined in @file{ptypes.h}.} */ tree t; /* @r{@code{tree} is defined in @file{ptypes.h}.} */
@} @}
@end group @end group
@@ -2999,7 +2999,7 @@ Let's go ahead and add the new @code{YYLTYPE} definition and the
@group @group
%union @{ %union @{
long int n; long n;
tree t; /* @r{@code{tree} is defined in @file{ptypes.h}.} */ tree t; /* @r{@code{tree} is defined in @file{ptypes.h}.} */
@} @}
@end group @end group
@@ -3052,7 +3052,7 @@ Thus, they belong in one or more @code{%code requires}:
@end group @end group
@group @group
%union @{ %union @{
long int n; long n;
tree t; /* @r{@code{tree} is defined in @file{ptypes.h}.} */ tree t; /* @r{@code{tree} is defined in @file{ptypes.h}.} */
@} @}
@end group @end group
@@ -3129,7 +3129,7 @@ sufficient. Instead, move its prototype from the unqualified
@end group @end group
@group @group
%union @{ %union @{
long int n; long n;
tree t; /* @r{@code{tree} is defined in @file{ptypes.h}.} */ tree t; /* @r{@code{tree} is defined in @file{ptypes.h}.} */
@} @}
@end group @end group
@@ -3706,7 +3706,7 @@ a preprocessor.
In most programs, you will need different data types for different kinds In most programs, you will need different data types for different kinds
of tokens and groupings. For example, a numeric constant may need type of tokens and groupings. For example, a numeric constant may need type
@code{int} or @code{long int}, while a string constant needs type @code{int} or @code{long}, while a string constant needs type
@code{char *}, and an identifier might need a pointer to an entry in the @code{char *}, and an identifier might need a pointer to an entry in the
symbol table. symbol table.