[PATCH] Prevent GCC 6 <cstdlib> from including /usr/include/stdlib.h
Andreas Schwab
schwab@suse.de
Mon Jun 13 07:35:00 GMT 2016
Florian Weimer <fweimer@redhat.com> writes:
> On 06/13/2016 09:20 AM, Andreas Schwab wrote:
>> Florian Weimer <fweimer@redhat.com> writes:
>>
>>> On 06/11/2016 12:07 AM, Roland McGrath wrote:
>>>> In what way is it not a bug for cstdlib to do #include_next <stdlib.h>?
>>>
>>> They are part of the implement in the same way we are. Why would it be a
>>> bug?
>>
>> Because <cstdlib> and <stdlib.h> are unrelated headers belonging to
>> different projects. Their place in the include order needs to be
>> controlled independently.
>
> They aren't unrelated, the C++ run-time is a superset of the C run-time. C
> headers have to be usable from C++, and C++ headers describing glibc
> functionality need to be compatible with glibc.
That doesn't make them related. They are located in independent include
directories, thus you cannot assume a fixed order.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
More information about the Libc-alpha
mailing list