tmp/tmpavfz28ph/{from.md → to.md}
RENAMED
|
@@ -0,0 +1,17 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
#### 30 undefined behavior <a id="defns.undefined">[[defns.undefined]]</a>
|
| 2 |
+
|
| 3 |
+
behavior for which this document imposes no requirements
|
| 4 |
+
|
| 5 |
+
[*Note 1 to entry*: Undefined behavior may be expected when this
|
| 6 |
+
document omits any explicit definition of behavior or when a program
|
| 7 |
+
uses an erroneous construct or erroneous data. Permissible undefined
|
| 8 |
+
behavior ranges from ignoring the situation completely with
|
| 9 |
+
unpredictable results, to behaving during translation or program
|
| 10 |
+
execution in a documented manner characteristic of the environment (with
|
| 11 |
+
or without the issuance of a diagnostic message), to terminating a
|
| 12 |
+
translation or execution (with the issuance of a diagnostic message).
|
| 13 |
+
Many erroneous program constructs do not engender undefined behavior;
|
| 14 |
+
they are required to be diagnosed. Evaluation of a constant expression
|
| 15 |
+
never exhibits behavior explicitly specified as undefined in [[intro]]
|
| 16 |
+
through [[cpp]] of this document [[expr.const]]. — *end note*]
|
| 17 |
+
|