[Bug c++/83624] Strong using deprecation warning in C++03

2018-02-16 Thread msebor at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83624 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug c++/83624] Strong using deprecation warning in C++03

2018-01-04 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83624 --- Comment #4 from Jonathan Wakely --- Because it's not non-standard, inline namespaces are standard. That means the compiler already supports them, and will continue to do so. Supporting a different (inferior) way to achieve something similar

[Bug c++/83624] Strong using deprecation warning in C++03

2018-01-03 Thread andysem at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83624 --- Comment #3 from andysem at mail dot ru --- As you noted, --pedantic-errors makes that code an error, so it is not an equivalent replacement. Also, GNU-specific attributes can and often are supported by other compilers. When they are not, the

[Bug c++/83624] Strong using deprecation warning in C++03

2018-01-03 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83624 --- Comment #2 from Jonathan Wakely --- (In reply to andysem from comment #0) > The problem with this warning is that it suggests using inline namespaces > instead, but that is not an option on C++03 code base. The attribute is used > precisely t

[Bug c++/83624] Strong using deprecation warning in C++03

2017-12-29 Thread andysem at mail dot ru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83624 --- Comment #1 from andysem at mail dot ru --- Created attachment 42983 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42983&action=edit Test code to reproduce the warning I've attached a repro test case. Compile with: g++ -std=gnu++03 -o