https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89232
--- Comment #7 from pere at hungry dot com ---
I just think it would have been useful if the compiler said something
like 'header file is not defined/available in C++' or
something like that. It would provide feedback to the develop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89232
--- Comment #5 from pere at hungry dot com ---
Thank you for the explanation. It is a lot clearer to me now.
One thing confuses me, though. If is not acceptable in C++,
why is there no warning from the compiler when it is included, instead of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89232
--- Comment #2 from pere at hungry dot com ---
Aha. I thought valid C code would also be valid C++ code, and this belief
became stronger when clang (and clang++) would accept the code. Is there a
list of C headers not supported by C++?
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: pere at hungry dot com
Target Milestone: ---
I ran into this issue while trying to prepare the coz profiler for Debian.
The header file seem to be inefficient when using cc and
clang, be
--- Additional Comments From pere at hungry dot com 2004-10-28 09:15 ---
The compiler on IA64/HP-UX (aCC: HP aC++/ANSI C B3910B A.05.50 [May 15 2003])
refuses to compile this code and gives this error message:
Error 271: "x.c", line 1 # Illegal initializer.
char
