[Bug driver/13071] no easy way to exclude backward C++ headers from include path

["redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=13071

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING

--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Harald van Dijk from comment #8)
> (In reply to Andrew Pinski from comment #7)
> > Isn't doing the extern "C" around standard C++ headers declared by the C++
> > standard as undefined behavior?
> 
> It is (as is doing extern "C++" around standard C++ headers, for that
> matter),

Where does it say that?

> but <complex.h> only became a standard C++ header in C++11. This
> bug is from 2003 and the comment before yours was from 2009, so I think
> <complex.h> was not a standard C++ header yet.

Agreed. But there is no complex.h in the backward directory now.

The contents of that directory are:

auto_ptr.h  backward_warning.h  binders.h  hash_fun.h  hash_map  hash_set 
hashtable.h  strstream

The <strstream> header is required for standard conformance, so excluding that
directory would make it impossible to use that standard header. The other
headers seem unlikely to conflict with any headers in /usr/include (which was
the original subject of this PR).

Can we close this now?

-- 
You are receiving this mail because:
You reported the bug.