J3/10-147 To: J3 Subject: Editorial repairs From: Van Snyder Date: 2010 April 01 Reference: N1814 Edits for agreement of number ----------------------------- [9.3.4.4p6 202:] Editor: Replace "data" by "a datum". Edits for the ATOM argument of ATOMIC_DEFINE and ATOMIC_REF ----------------------------------------------------------- We regularized the description of the type and kind of arguments, and then ATOMIC_DEFINE and ATOMIC_REF used the old turgid style. [13.7.20p3] In the description of the ATOM argument replace "coarray or coindexed object and of type integer" by "integer coarray or coindexed object". [13.7.21p3] In the description of the ATOM argument replace "coarray or coindexed object and of type integer" by "integer coarray or coindexed object". Edits for DIM argument of CSHIFT and EOSHIFT -------------------------------------------- In the description of the DIM argument of the CSHIFT and EOSHIFT intrinsic functions, the word "omitted" is used. The correct word here is "absent". Or... "omitted" was intentional and we didn't do anything about the absent case -- e.g., disassociated pointer corresponding to nonpointer optional dummy -- in which case we probably need an interp. [13.7.43p3 340:] Editor: In the description of the DIM argument, replace "omitted" by "absent". [13.7.52p3 344:] Editor: In the description of the DIM argument, replace "omitted" by "absent". Edits for DIM argument of LCOBOUND and UCOBOUND ----------------------------------------------- Other intrinsic functions that require an integer scalar argument say "shall be an integer scalar." LCOBOUND and UCOBOUND say "shall be a scalar and of type integer." [13.7.91p3 360:] Editor: In the description of the DIM argument, replace "a scalar and of type integer" by "an integer scalar". [13.7.172p3 395:] Editor: In the description of the DIM argument, replace "a scalar and of type integer" by "an integer scalar". Edits for PRESENT ----------------- [13.7.132p3] In the first sentence of the argument description paragraph, insert "The actual argument" before "A" so as not to lead to confusion when later discussing the dummy argument A. In the second sentence of the argument description paragraph, insert "or allocatable" after "a pointer". Alternatively, replace "be a pointer" by "have any attributes" which covers pointer and allocatable and anything we add in the future.