From c226d4ed48b13551f0fface838ccffae8b1e14c9 Mon Sep 17 00:00:00 2001 From: Akim Demaille Date: Sun, 12 Aug 2018 15:00:35 +0200 Subject: [PATCH] style: doc: remove useless reference to 'int' in integral types * doc/bison.texi: Prefer 'unsigned' to 'unsigned int'. Likewise for long and short. --- TODO | 2 +- doc/bison.texi | 12 ++++++------ 2 files changed, 7 insertions(+), 7 deletions(-) diff --git a/TODO b/TODO index c25df084..f150cbd4 100644 --- a/TODO +++ b/TODO @@ -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 toknum: - const unsigned short int + const unsigned short parser::yytoken_number_[] = { 0, 256, 257, 258, 259, 260, 261, 262, 263, 264, diff --git a/doc/bison.texi b/doc/bison.texi index 74ad9e5d..9f16f730 100644 --- a/doc/bison.texi +++ b/doc/bison.texi @@ -2883,7 +2883,7 @@ can be done with two @var{Prologue} blocks, one before and one after the @group %union @{ - long int n; + long n; tree t; /* @r{@code{tree} is defined in @file{ptypes.h}.} */ @} @end group @@ -2935,7 +2935,7 @@ Look again at the example of the previous section: @group %union @{ - long int n; + long n; tree t; /* @r{@code{tree} is defined in @file{ptypes.h}.} */ @} @end group @@ -2999,7 +2999,7 @@ Let's go ahead and add the new @code{YYLTYPE} definition and the @group %union @{ - long int n; + long n; tree t; /* @r{@code{tree} is defined in @file{ptypes.h}.} */ @} @end group @@ -3052,7 +3052,7 @@ Thus, they belong in one or more @code{%code requires}: @end group @group %union @{ - long int n; + long n; tree t; /* @r{@code{tree} is defined in @file{ptypes.h}.} */ @} @end group @@ -3129,7 +3129,7 @@ sufficient. Instead, move its prototype from the unqualified @end group @group %union @{ - long int n; + long n; tree t; /* @r{@code{tree} is defined in @file{ptypes.h}.} */ @} @end group @@ -3706,7 +3706,7 @@ a preprocessor. In most programs, you will need different data types for different kinds 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 symbol table.