Re: Bug: gcc/cp/parse.y & gcc/cp/decl.h: Conflict on TYPENAME

[Akim Demaille <akim at epita dot fr>]

Can someone provide me with feedback please.  Should I register a PR
for this bug?

| The following patch supersedes my previous patch: it addresses two
| parser related issues: one is that:
| 
| | | The parser declares token TYPENAME and decl.h declares an enum
| | | including TYPENAME.  Several files include both, what results in a
| | | dangerous clash.
| | | 
| | | Given the risks, I suggest that the parser slowly moves to using the
| | | `tFOO' convention, so, amongst the various possible changes, I
| | | preferred this one: instead of token TYPENAME, using token tTYPENAME.
| | | If you have another preference, please tell me, I'll adjust the patch
| | | accordingly.
| |
| | Without this patch, expect next Bison to create a failure of the
| | compilation: it nows outputs the tokens as enums (when __STDC__), and
| | therefore, the compilation will fail (as is to be expected from id
| | clashes).
|