https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82417
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82417
--- Comment #5 from Jonathan Wakely ---
Author: redi
Date: Tue Oct 10 11:25:45 2017
New Revision: 253581
URL: https://gcc.gnu.org/viewcvs?rev=253581=gcc=rev
Log:
PR libstdc++/82417 do not include C99 in strict modes
As an extension the C++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82417
--- Comment #4 from Jonathan Wakely ---
I'm not opposed to a warning in principle, but I'd prefer it to be one
controllable by a -Wxxx option. I don't know how to do that using the
preprocessor, so we'd have to do something like:
#ifndef
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82417
--- Comment #3 from Marc Glisse ---
(In reply to Jonathan Wakely from comment #2)
> Thinking about this further, I think we must not include at all
> for strict -std=c++1* modes,
Yes.
Can we get a #warning in that case which explains that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82417
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82417
--- Comment #1 from Marc Glisse ---
(In reply to Jonathan Wakely from comment #0)
> The C++11 standard says that should just include the C++
> header and completely ignore the C library's header.
I am very surprised that nobody has cared
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82417
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
