[PATCH v3 3/7] Assume support for __extension__ ({ })

[Arsen Arsenović]

Paul Eggert <eggert@cs.ucla.edu> writes:

> 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).

In addition, AFAIK, requirements for installed headers and for libc code
is different in that the installed headers should work with any C
compiler in all cases.
-- 
Arsen Arsenović
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 418 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20251110/ebdb7c40/attachment.sig>