(j3.2006) Lock variables

[Van Snyder]

On Mon, 2009-03-09 at 17:30 -0700, Malcolm Cohen wrote:
> Again, Fortran 90/95 disallow all (intrinsic) i/o (including 
> unformatted) of types with private components, and I cannot believe
> such a stupid feature was a deliberate part of F2003.  Evidence
> please, on a postcard.

See 01-173r1, which applied edits to 01-007.

The paragraph

[01-007:21-23]
   "Unless a list item is processed by a user-defined derived-type
input/output procedure (9.5.4.4.3), a derived-type object shall not
appear as an input/output list item if any component ultimately in the
object is not accessible within the scoping unit containing the
input/output statement."

was replaced by that paper with essentially the present wording, which
has been moved around and bulletized between then and now, but not
changed since 01-007r1 in a substantive way.

The introductory paragraph appears to say it was intentional.

"The description of how to expand list items into effective list items,
or just expand a list item as if the user had specified ...., is broken
and/or incompletely specified, and/or specifies undesirable
behavior,...."

It seems we need an interp of the form "Did we really intend to do
this?"

Rich Bleikamp, if you're listening, is this what you intended?