https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65473
--- Comment #5 from Jonathan Wakely redi at gcc dot gnu.org ---
But there's no such thing as a detection macro in the standard, so it's not
going to talk about where they belong.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65473
--- Comment #4 from Louis Dionne ldionne.2 at gmail dot com ---
(In reply to Jonathan Wakely from comment #3)
(In reply to Louis Dionne from comment #2)
Does the standard specify which headers should define those macros?
Of course not,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65473
--- Comment #3 from Jonathan Wakely redi at gcc dot gnu.org ---
(In reply to Louis Dionne from comment #2)
Does the standard specify which headers should define those macros?
Of course not, __GLIBCXX__ is not specified by the standard at all.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65473
--- Comment #2 from Louis Dionne ldionne.2 at gmail dot com ---
Does the standard specify which headers should define those macros? If not,
then it's a QOI issue that could easily be solved. In all cases, does stdcxx
document which headers must
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65473
--- Comment #1 from Jonathan Wakely redi at gcc dot gnu.org ---
(In reply to Louis Dionne from comment #0)
One would expect that including _any_ header from the standard library
defines the relevant detection macros.
That's not true for most
