(j3.2006) Fwd: e-mail to j3 list

[Dan Nagle]

Hi,

Dick is having trouble posting so I'm forwarding this for him.

> Begin forwarded message:
> 
> From: Dick Hendrickson <dick.hendrickson at gmail.com>
> Subject: Re: e-mail to j3 list
> Date: October 6, 2016 at 12:05:26 MDT
> To: Dan Nagle <danlnagle at me.com>
> 
> On Sat, Oct 1, 2016 at 3:34 AM, Robert Corbett <robert.corbett at oracle.com <mailto:robert.corbett at oracle.com>> wrote:
> 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.
>  
> [9.6.4, not 12.6.4]
> 
> I don't know.  Bullet (11) says that if an error or end condition occurs processing continues as specified in 9.11 and in 9.11.2 (2) it says that io do variables in the statement become undefined.  This happens either during execution of the I/O statement or at a subsequent WAIT operation.  
> 
> Does it matter?  If the do variable becomes undefined the program can't reference it until it becomes defined, so there's no need worry. 
> 
> This is from F2008, things might have changed by now.
> 
> 


--

Cheers!
Dan Nagle




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.j3-fortran.org/pipermail/j3/attachments/20161006/17c9b6c0/attachment.html