|
From: | Paul Eggert |
Subject: | Re: Don't #include gnulib-generated .h files from config.h |
Date: | Sat, 24 Sep 2022 16:48:16 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 |
On 9/24/22 16:10, Bruno Haible wrote:
Thus, it's best to avoid such a situation. This holds not only for <stdalign.h> but also for <stdbool.h>. For <assert.h> on the other hand I think the trouble is limited, because <assert.h> always exists among the system header files.
These days stdbool.h falls into pretty much the same category as assert.h. As far as I know, every platform currently supported by Gnulib that doesn't have a working bool builtin (and thus will include stdbool.h) has a stdbool.h that should work well enough for all but the most contrarian of uses. So I suggest leaving stdbool.h alone. That way, we'll have better luck with Autoconf and AC_C_BOOL.
stdalign.h is more of a problem as it was introduced in C11 and Gnulib doesn't require C11 yet, so we will need a fix along the lines of what you suggested, though I wish the code duplication could be avoided.
[Prev in Thread] | Current Thread | [Next in Thread] |