Re: How can Autoconf help with the transition to stricter compilation defaults?
Ben Boeckel <[email protected]> Tue, 15 Nov 2022 18:43:00 -0500
| Newsgroups | dev.linux.lists.c-std-porting |
|---|---|
| Message-ID | <Y3QkBBcMbQgwadA+@farprobe> |
On Tue, Nov 15, 2022 at 15:09:19 -0800, Paul Eggert wrote:
> This may be a hack, but it's a *good* hack. It's likely to fix
> real-world bugs that would be caused if Clang becomes overly pedantic by
> default here. And the probability of introducing real-world bugs is
> essentially zero.
FWIW, CMake uses the same signature for detecting whether a function
exists or not:
https://gitlab.kitware.com/cmake/cmake/-/blob/master/Modules/CheckFunctionExists.c
It's also been like this (without the `void`) for 20 years; the `void`
argument was added 6 years ago:
https://gitlab.kitware.com/cmake/cmake/-/commits/master/Modules/CheckFunctionExists.c
--Ben