“Execution sequence” is inappropriate phraseology
6.9.1 [intro.execution]

Created on 2009-03-03.00:00:00 last changed 144 months ago


Date: 2009-10-15.00:00:00

[Voted into WP at October, 2009 meeting.]

Date: 2009-09-15.00:00:00

Proposed resolution (September, 2009):

  1. Change 6.9.1 [intro.execution] paragraph 3 as follows:

  2. ...An instance of the abstract machine can thus have more than one possible execution sequence for a given program and a given input.
  3. Change 6.9.1 [intro.execution] paragraph 5 as follows:

  4. A conforming implementation executing a well-formed program shall produce the same observable behavior as one of the possible execution sequences executions of the corresponding instance of the abstract machine with the same program and the same input. However, if any such execution sequence contains an undefined operation, this International Standard places no requirement on the implementation executing that program with that input (not even with regard to operations preceding the first undefined operation).
  5. Delete 6.9.1 [intro.execution] paragraph 6, including the footnote:

  6. The observable behavior of the abstract machine is its sequence of reads and writes to volatile data and calls to library I/O functions. [Footnote: An implementation can offer additional library I/O functions as an extension. Implementations that do so should treat calls to those functions as “observable behavior” as well. —end footnote]
  7. Change 6.9.1 [intro.execution] paragraph 9 as follows:

  8. The least requirements on a conforming implementation are:

    • Access to volatile objects are evaluated strictly according to the rules of the abstract machine.

    • At program termination, all data written into files shall be identical to one of the possible results that execution of the program according to the abstract semantics would have produced.

    • The input and output dynamics of interactive devices shall take place in such a fashion that prompting messages actually appear prior to a program waiting prompting output is actually delivered before a program waits for input. What constitutes an interactive device is implementation-defined.

    These collectively are referred to as the observable behavior of the program. [Note: more stringent correspondences between abstract and actual semantics may be defined by each implementation. —end note]

(Note; this resolution also resolves issue 612.)

Date: 2009-03-03.00:00:00
N2800 comment US 16
N2800 comment UK 8
N2800 comment UK 7

In the presence of threads, it is no longer appropriate to characterize the abstract machine as having an “execution sequence.”

Date User Action Args
2010-03-29 00:00:00adminsetstatus: dr -> cd2
2009-11-08 00:00:00adminsetmessages: + msg2413
2009-11-08 00:00:00adminsetstatus: tentatively ready -> dr
2009-09-29 00:00:00adminsetmessages: + msg2285
2009-09-29 00:00:00adminsetstatus: drafting -> tentatively ready
2009-08-03 00:00:00adminsetstatus: open -> drafting
2009-03-03 00:00:00admincreate