This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/20366] Compilation errors in installed headers in strict-compliance modes
- From: "zackw at panix dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 13 Jul 2016 20:43:05 +0000
- Subject: [Bug libc/20366] Compilation errors in installed headers in strict-compliance modes
- Auto-submitted: auto-generated
- References: <bug-20366-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20366
--- Comment #2 from Zack Weinberg <zackw at panix dot com> ---
(In reply to Andreas Schwab from comment #1)
> I don't think it makes sense to use these extension headers in a strict C
> environment. Strict C also means to restrict to the facilities defined by
> the standard.
Nearly all of glibc's headers go out of their way to be usable in a strict C
environment; whether or not you think it makes sense for any particular header
to _be used_ in a strict C environment, consistency dictates that they should
all be _usable_.
Also, the necessary fixes are straightforward and, in general, things that
should be done anyway (don't use legacy unsigned integer typedefs; do use
__foo_t; include all headers necessary for the header to be usable in
isolation).
--
You are receiving this mail because:
You are on the CC list for the bug.