On Tue, 13 Jun 2023, Paul Eggert wrote: > > There is always the possibility to have the header co-owned by both > > the compiler and C library, limits.h style. > > Just > > #if __has_include_next(<stdckdint.h>) > > # include_next <stdckdint.h> > > #endif > > I don't see how you could implement __has_include_next(<stdckdint.h>) for > arbitrary non-GCC compilers, which is what we'd need for glibc users. For > glibc internals we can use "#include_next" more readily, since we assume a > new-enough GCC. I.e. we could do something like this:
Given the possibility of library functions being included in <stdckdint.h> in future standard versions, it seems important to look at ways of splitting responsibility for the header between the compiler and library, whether with __has_include_next, or compiler version conditionals, or some other such variation. -- Joseph S. Myers jos...@codesourcery.com
