tmp/tmpo9vv01cb/{from.md → to.md}
RENAMED
|
@@ -1,15 +1,15 @@
|
|
| 1 |
-
###
|
| 2 |
|
| 3 |
-
|
| 4 |
-
|
| 5 |
-
|
| 6 |
-
|
| 7 |
-
|
| 8 |
-
|
| 9 |
-
|
| 10 |
-
|
| 11 |
-
|
| 12 |
-
|
| 13 |
-
|
| 14 |
-
|
| 15 |
|
|
|
|
| 1 |
+
### [[except]]: exception handling <a id="diff.cpp14.except">[[diff.cpp14.except]]</a>
|
| 2 |
|
| 3 |
+
**Change:** Remove dynamic exception specifications. **Rationale:**
|
| 4 |
+
Dynamic exception specifications were a deprecated feature that was
|
| 5 |
+
complex and brittle in use. They interacted badly with the type system,
|
| 6 |
+
which became a more significant issue in this International Standard
|
| 7 |
+
where (non-dynamic) exception specifications are part of the function
|
| 8 |
+
type. **Effect on original feature:** A valid C++14 function
|
| 9 |
+
declaration, member function declaration, function pointer declaration,
|
| 10 |
+
or function reference declaration, if it has a potentially throwing
|
| 11 |
+
dynamic exception specification, will be rejected as ill-formed in this
|
| 12 |
+
International Standard. Violating a non-throwing dynamic exception
|
| 13 |
+
specification will call `terminate` rather than `unexpected` and might
|
| 14 |
+
not perform stack unwinding prior to such a call.
|
| 15 |
|