tmp/tmpg8jexnqv/{from.md → to.md}
RENAMED
|
@@ -3,19 +3,21 @@
|
|
| 3 |
The semantic descriptions in this document define a parameterized
|
| 4 |
nondeterministic abstract machine. This document places no requirement
|
| 5 |
on the structure of conforming implementations. In particular, they need
|
| 6 |
not copy or emulate the structure of the abstract machine. Rather,
|
| 7 |
conforming implementations are required to emulate (only) the observable
|
| 8 |
-
behavior of the abstract machine as explained below.[^
|
| 9 |
|
| 10 |
Certain aspects and operations of the abstract machine are described in
|
| 11 |
this document as implementation-defined (for example, `sizeof(int)`).
|
| 12 |
These constitute the parameters of the abstract machine. Each
|
| 13 |
implementation shall include documentation describing its
|
| 14 |
-
characteristics and behavior in these respects.[^
|
| 15 |
-
|
| 16 |
-
|
|
|
|
|
|
|
| 17 |
|
| 18 |
Certain other aspects and operations of the abstract machine are
|
| 19 |
described in this document as unspecified (for example, order of
|
| 20 |
evaluation of arguments in a function call [[expr.call]]). Where
|
| 21 |
possible, this document defines a set of allowable behaviors. These
|
|
@@ -51,7 +53,7 @@ The least requirements on a conforming implementation are:
|
|
| 51 |
|
| 52 |
These collectively are referred to as the *observable behavior* of the
|
| 53 |
program.
|
| 54 |
|
| 55 |
[*Note 2*: More stringent correspondences between abstract and actual
|
| 56 |
-
semantics
|
| 57 |
|
|
|
|
| 3 |
The semantic descriptions in this document define a parameterized
|
| 4 |
nondeterministic abstract machine. This document places no requirement
|
| 5 |
on the structure of conforming implementations. In particular, they need
|
| 6 |
not copy or emulate the structure of the abstract machine. Rather,
|
| 7 |
conforming implementations are required to emulate (only) the observable
|
| 8 |
+
behavior of the abstract machine as explained below.[^5]
|
| 9 |
|
| 10 |
Certain aspects and operations of the abstract machine are described in
|
| 11 |
this document as implementation-defined (for example, `sizeof(int)`).
|
| 12 |
These constitute the parameters of the abstract machine. Each
|
| 13 |
implementation shall include documentation describing its
|
| 14 |
+
characteristics and behavior in these respects.[^6]
|
| 15 |
+
|
| 16 |
+
Such documentation shall define the instance of the abstract machine
|
| 17 |
+
that corresponds to that implementation (referred to as the
|
| 18 |
+
“corresponding instance” below).
|
| 19 |
|
| 20 |
Certain other aspects and operations of the abstract machine are
|
| 21 |
described in this document as unspecified (for example, order of
|
| 22 |
evaluation of arguments in a function call [[expr.call]]). Where
|
| 23 |
possible, this document defines a set of allowable behaviors. These
|
|
|
|
| 53 |
|
| 54 |
These collectively are referred to as the *observable behavior* of the
|
| 55 |
program.
|
| 56 |
|
| 57 |
[*Note 2*: More stringent correspondences between abstract and actual
|
| 58 |
+
semantics can be defined by each implementation. — *end note*]
|
| 59 |
|