https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82503
Bug ID: 82503
Summary: Warn on inclusion of <ccomplex> or <complex.h>
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
From Bug 82417 comment 3:
Can we get a #warning in that case which explains that including <complex.h>
in strict C++11+ mode makes no sense? Actually, <ccomplex> could also do with
a #warning explaining that it never makes sense to include it.
The reasoning is that <ccomplex> is identical to <complex>, except for being
deprecated. There's no reason to ever prefer <ccomplex> to <complex>.
In strict C++11+ modes the header <complex.h> is identical to <ccomplex> so the
same argument applies.
