Closed rconde01 closed 3 years ago
There are a couple approaches that could be taken:
1) replace throw() with noexcept, and throw(...) with noexcept(false) 2) create something like a THROW_SPEC macro that expands to the current code or the above code depending on the detected CPP version (or additionally a user settable macros).
Closing this issue as unable to address -- for now. We plan to support C++17 features once g++ catches up with the standard.
I'm not sure what you mean? g++ supports C++17 for a very long time.
g++ has some C++17 support, but not the complete standard. Until they reach full compliance, we can't make the leap.
The use of dynamic exception specifications was removed in C++17:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0003r5.html
Therefore to allow compilation with C++17, they should be removed.