diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2025-03-21 10:48:10 +0100 |
|---|---|---|
| committer | Jakub Jelinek <jakub@gcc.gnu.org> | 2025-03-21 10:48:10 +0100 |
| commit | 3355e44dd2b35488facfec66aad628c5999c89d6 (patch) | |
| tree | fde6d216501f2b25cd7015964805d5db3a3527e7 /gcc/tree-loop-distribution.cc | |
| parent | ff3343518ae6e1aa1efe7fe02a6a4c6cb24f3b62 (diff) | |
| download | gcc-3355e44dd2b35488facfec66aad628c5999c89d6.zip gcc-3355e44dd2b35488facfec66aad628c5999c89d6.tar.gz gcc-3355e44dd2b35488facfec66aad628c5999c89d6.tar.bz2 | |
cobol: Rename COB_{BLOCK,UNSIGNED,SIGNED} to {BLOCK,UNSIGNED,SIGNED}_kw for consistency
On Wed, Mar 19, 2025 at 06:03:24PM -0400, James K. Lowden wrote:
> Elsewhere in the parser where there was a conflict like that, I renamed
> the token. For example, the COBOL word TRUE uses a token named
> TRUE_kw. I don't mind either way; your solution has less impact on the
> parser.
I think consistency is good and when it is a suffix rather than prefix,
it also sorts alphabetically together with the actual keywords.
2025-03-21 Jakub Jelinek <jakub@redhat.com>
* parse.y: Rename COB_BLOCK to BLOCK_kw, COB_SIGNED to SIGNED_kw and
COB_UNSIGNED to UNSIGNED_kw.
* scan.l: Likewise.
* token_names.h: Regenerate.
Diffstat (limited to 'gcc/tree-loop-distribution.cc')
0 files changed, 0 insertions, 0 deletions