[Bug c++/4898] adding an option to verify exception specifications [-Wexceptions]

2020-11-05 Thread egallager at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=4898 Eric Gallager changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug c++/4898] adding an option to verify exception specifications [-Wexceptions]

2019-02-22 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=4898 --- Comment #10 from Eric Gallager --- (In reply to Jonathan Wakely from comment #9) > Why a new warning instead of making -Wterminate handle throw() as well as > noexcept ? For consistency with clang? I dunno, I guess putting it under -Wterminat

[Bug c++/4898] adding an option to verify exception specifications [-Wexceptions]

2019-02-22 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=4898 --- Comment #9 from Jonathan Wakely --- Why a new warning instead of making -Wterminate handle throw() as well as noexcept ?

[Bug c++/4898] adding an option to verify exception specifications [-Wexceptions]

2019-02-22 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=4898 Eric Gallager changed: What|Removed |Added Blocks||87403 Summary|adding an option

[Bug c++/4898] adding an option to verify exception specifications

2018-08-22 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=4898 --- Comment #7 from Jonathan Wakely --- (In reply to Martin Sebor from comment #2) > I agree a new warning would be useful. For example, the following code should > be diagnosed: > > struct S { S () throw () { throw 0; } }; This is still relevan

[Bug c++/4898] adding an option to verify exception specifications

2018-08-22 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=4898 --- Comment #6 from Jonathan Wakely --- Yes, but IMHO it would be a huge waste of time to add a ton of new machinery to the compiler to check for "correct" usage of an obsolete feature. Most C++98 code didn't even use them, because they were not u

[Bug c++/4898] adding an option to verify exception specifications

2018-08-22 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=4898 --- Comment #5 from Eric Gallager --- (In reply to Jonathan Wakely from comment #4) > Dynamic exception specifications are no longer part of the C++ language > anyway. Well, in newer standards at least, but they were at one point in an older stan

[Bug c++/4898] adding an option to verify exception specifications

2017-08-22 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=4898 --- Comment #4 from Jonathan Wakely --- Dynamic exception specifications are no longer part of the C++ language anyway.

[Bug c++/4898] adding an option to verify exception specifications

2017-08-22 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=4898 Eric Gallager changed: What|Removed |Added CC||egallager at gcc dot gnu.org --- Comment

[Bug c++/4898] adding an option to verify exception specifications

2008-07-21 Thread sebor at roguewave dot com
--- Comment #2 from sebor at roguewave dot com 2008-07-21 16:17 --- I agree a new warning would be useful. For example, the following code should be diagnosed: struct S { S () throw () { throw 0; } }; as should this: struct S { S () throw (int) { throw ""; } }; -- http://gcc.gnu.