07-134

To:          J3
Subject:     Comments on Annex A
From:        Van Snyder
Date: 2007 January 25

1 Edits

Edits refer to 07-007. Page and line numbers are displayed in the margin.
Absent other instructions, a page and line number or line number range
implies all of the indicated text is to be replaced by associated text,
while a page and line number followed by + (-) indicates that associated
text is to be inserted after (before) the indicated line. Remarks are
noted in the margin, or appear between [ and ] in the text.

[505:25] -----------------------------------------------------------------
[Editor: Replace "to" by "that may be associated with".]

[506:20] -----------------------------------------------------------------
[Editor: Replace "an" by "a scalar".]

[506:35] -----------------------------------------------------------------
[Editor: Delete ", and whether it is optional" because that's already
said at [506:29].]

[507:23,25,27]------------------------------------------------------------
[Editor: Insert a blank, as needed, after "1539", thrice.]

[508:17-18] --------------------------------------------------------------
[Editor: Replace "will be" by "is".]

[508:28] -----------------------------------------------------------------
[Editor: Replace "on . . . statements" by "in a variable definition
context (16.6.7)".]

[509:1-2] ----------------------------------------------------------------
[Editor: Insert "may" before "have" and "or is a procedure pointer, and
to which procedures may be bound" after the final "type".]

[509:12] -----------------------------------------------------------------
[Editor: Insert "to be" after "specified".]

[509:23] -----------------------------------------------------------------
[Editor: Insert ", BLOCK" after "ASSOCIATE".]

[509:32-34] --------------------------------------------------------------
[Editor: Insert "at its point of interface" after "explicit interface"
and either replace "a procedure reference . . . unit" by "the reference
is to a procedure from within its own scoping unit" or delete that phrase
and add a new sentence "A procedure has explicit interface within its own
scoping unit."]

[513:32] -----------------------------------------------------------------
[Editor: Insert ", an ALLOCATE statement" after "pointer assignment
statement" and replace "the execution of an" by "an intrinsic".]

[514:11] -----------------------------------------------------------------
[Editor: Insert ", its binding label (if any)" after "argument".]

[514:18-19] --------------------------------------------------------------
[Editor: Replace "fundamental" by "largest-scale" since some consider
"fundamental" to mean "indivisible", and insert ", submodule" after
"module".]

[514:37-38] --------------------------------------------------------------
[Editor: Join the lines.]

[515:15-17] --------------------------------------------------------------
[Editor: Replace "in . . . as" by "as a", "parameters" by "parameter",
"bounds" by "bound" and append "in a type declaration statement in a
procedure" within and at the end of the sentence.]

[516:3] ------------------------------------------------------------------
[Editor: Replace "subcomponent . . . object" by "component of an object
of derived type" because none of the other glossary entries repeat what
they're defining in the way this one does.]

[516:31] -----------------------------------------------------------------
[Editor: Replace "binding in" by "bound to" because a binding isn't a
procedure.]

[517:7] ------------------------------------------------------------------
[Editor: Append another sentence "For a pointer, the property of not
having a determinate association status."]

2 Questions without comments
[506:30-33] --------------------------------------------------------------
Do we need to say something about co-arrays and co-rank?