This is the mail archive of the
mailing list for the glibc project.
Re: stdio.h vs. bits/stdio.h header brokeness?
> According to the ChangeLog, the one in bits/stdio.h must be wrong.
> I append a patch to fix this.
But, isn't __THROW expanded to throw() when compiling C++ code, to let
the compiler know that these functions never will throw exceptions?
Why is it wrong to include this when compiling C++?
Or did you think about the following changelog entry?
1999-11-23 Andreas Jaeger <firstname.lastname@example.org>
* include/aio.h: Remove __THROW from internal interfaces. __THROW
is only need in external header files that might be compiled by a
Doesn't this indicating that the stdio.h header file should use
__THROW(), as it is an external header file, and that bits/stdio.h
need to do the same to avoid compiler warnings?