|
From: | Paul Eggert |
Subject: | Re: [PATCH 0/3] yacc: compute the best type for the state number |
Date: | Wed, 2 Oct 2019 13:46:07 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.0 |
On 10/2/19 10:55 AM, Kaz Kylheku wrote:
Over time, POSIX has invented new identifiers that didn't follow any namespace pattern. Or they suddenly invented new namespace prefixes, unpredictably. We've survived.
To be fair, they've largely done this only when you include a POSIX header.
If some new_fangled_t is introduced into <sys/types.h> in 2050, there will be some -DPOSIX_SOURCE=20500112 or whatever to enable its visibility, and that of any function prototypes which use it.
There's no need for an implementation to do that since _t is reserved, and in practice many implementations don't do it.
"Conforming applications shall not use names beginning in yy or YY since the yacc parser uses such names."
Sorry, I didn't know that.
[Prev in Thread] | Current Thread | [Next in Thread] |