[PATCH v3 3/7] Assume support for __extension__ ({ })
Paul Eggert
eggert@cs.ucla.edu
Mon Nov 10 16:39:12 GMT 2025
On 2025-11-10 06:17, Alejandro Colomar wrote:
> -# elif !defined __GNUC__ || defined __STRICT_ANSI__
> +# elif defined __STRICT_ANSI__
This assumes the user's C compiler supports statement expressions. This
may be going a bridge too far: although statement expressions are
supported by every C compiler I know of in common use with glibc, they
are not part of the C standard and if we make this change we might
exclude compilers we don't know about, or exclude future compilers.
Also, starting to use statement expressions now might run into bugs in
existing non-GCC C compilers.
If we are to make changes like this, there should be a NEWS item about
it, and it should be documented in the manual (as per my previous email
in this thread).
More information about the Libc-alpha
mailing list