Craig Dedo CAPM
Tue Jan 26 21:58:28 EST 2016
Why did we prohibit mixing Asynchronous I/O and User-Defined Derived Type I/O
(UDDTIO)? In a private conversation with Richard Bleikamp, the main author of the UDDTIO
feature, I asked him this very question. His answer was very simple and straightforward.
He said, "Because it's too damned hard! I have no idea how we would implement such a
Please feel free to contact me at any time with any questions or concerns that
you may have. I am looking forward to hearing from you soon.
Craig T. Dedo, CAPM
17130 W. Burleigh Place
P. O. Box 423 Mobile Phone: (414) 412-5869
Brookfield, WI 53008-0423 E-mail: < <mailto:craig at ctdedo.com> craig at ctdedo.com>
Linked-In: <http://www.linkedin.com/in/craigdedo> http://www.linkedin.com/in/craigdedo
> -----Original Message-----
> From: j3-bounces at mailman.j3-fortran.org [mailto:j3-bounces at mailman.j3-fortran.org]
> On Behalf Of Bill Long
> Sent: Tuesday, January 26, 2016 14:06
> To: Van Snyder; fortran standards email list for J3
> Subject: Re: (j3.2006) 16-126
> On Jan 26, 2016, at 1:43 PM, Van Snyder < <mailto:Van.Snyder at jpl.nasa.gov>
Van.Snyder at jpl.nasa.gov> wrote:
> > On Tue, 2016-01-26 at 19:36 +0000, Bill Long wrote:
> >> Paper 16-126 on mixing defined I/O and asynchronous I/O seems to have
> >> missed this restriction: "Neither a parent nor child data transfer
> >> statement shall be asynchronous."
> > Good catch. One less interp to worry about.
> > But why did we do that? There's no harm in it?
> It is probably too big of a hammer. For example, defined I/O for a file opened for
> read only, and asynchronous, is not too hard to handle. Of course, you can always
> do the I/O directly, not using defined I/O procedures, and it works fine. But I
> imagine that OOP programmers would prefer type-bound defined I/O.
> Bill Long
> <mailto:longb at cray.com> longb at cray.com
> Fortran Technical Support & voice: 651-605-9024
> Bioinformatics Software Development fax: 651-605-9142
> Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101
> J3 mailing list
> <mailto:J3 at mailman.j3-fortran.org> J3 at mailman.j3-fortran.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the J3