3 ms·
Ah yes, N2625 "What we think we reserve". Basically any C program containing variable or function "top", "END", "strict", "member" and so on is non-conforming a
by 112233 9mo ago
Ah yes, N2625 "What we think we reserve". Basically any C program containing variable or function "top", "END", "strict", "member" and so on is non-conforming and subject to undefined behaviour, so they define "potentially reserved" identifiers and as usual compiler vendors go and do the sane right thing.
- aw1621107 9mo agoThat paper isn't relevant here. From the paper (emphasis added): > 7.1.3 Reserved Identifiers > [snip] > Macro names and identifiers with external linkage that are specified in the C standard library clauses. > This proposal does not propose any changes to these reserved identifiers. Furthermore, that paper doesn't make the use of reserved external identifiers not UB, so there's no change there either.