(j3.2006) Asynchronous I/O question

Robert Corbett robert.corbett
Sat Oct 1 04:34:50 EDT 2016


On 9/30/2016 10:37 PM, Van Snyder wrote:
> A <do-variable> in an input/output item list is not a statement or
> construct entity.
>
> If it appears in an asynchronous input/output statement, should it be
> included among the pending input/output storage sequence (12.6.2.5p5-6)?
>
> Should it have the ASYNCHRONOUS attribute?

In 12.6.4.1, item (6) of the list operations establishes the "set"
of storage units identified by the input/output list.  (The word "set"
implies no ordering.  Because the order matters, "sequence" would be
better.)  Item (7) initiates asynchronous data transfer.  My reading
is that items (1) - (6) must complete before execution of the data
transfer statement completes, which means that execution is synchronous
before execution of item (7) begins.  Therefore, there is no need for
<do-variable> to have the ASYNCHRONOUS attribute or to be treated as
being among the pending input/output storage sequence.

Bob Corbett



More information about the J3 mailing list