ISO/IEC JTC 1/SC22/WG5 N1887

         Changes to N1869 to create N1885 (the DTS Ballot Draft)

                           Bill Long

                         18 October 2011


This paper details the changes made to the PDTR ballot draft of TR
29113, Further Interoperability of Fortran with C, to create the DTS
ballot draft for TS 29113. The paper is divided into three parts:

1) Changes that resulted from comments to the PDTR ballot (results in
   N1880), from the two countries that submitted comments. Comments
   from the UK are collected in N1881, and here identified
   sequentially as comments GB1 ... GB51. Comments from Germany are
   collected in N1882, and here identified as DIN1 ... DIN4.

2) Changes to conform to ISO rules.

3) Other edits.

Almost all of the edits came from papers submitted to J3 meeting
196. Those papers are identified by J3/11-nnn, where nnn is a paper
number.

Editorial commentary is enclosed in { }.

The edit citations refer to N1869.

----------------------------------------------------

Part 1: Changes resulting from PDTR Ballot Comments:

J3/11-231r2 - Edits for GB comments not in other papers. {Done}
              {Edit for GB28 changed to apply to both examples.}

J3/11-232r2 - Edits for GB6 and GB7. {Done}
	      {Added edit: In 5.3.5.1, last para, line 1: Change
	      "indicates if an error" to "indicates whether an
	      error".}

J3/11-234r2 - Edits for GB30, GB31, and GB32. {Done}

J3/11-235r2 - Edits for GB3. {Done}

J3/11-236r1 - Edits for GB10 and GB11. {Done}

J3/11-238r2 - Edits for GB36. {Done}

J3/11-239   - Edits for GB20. {Done}

J3/11-240r2 - Edits for GB48. {Done}

J3/11-244r2 - Edits for GB37, GB38, and GB39. {Done}

J3/11-248 -   Edits for DIN2.  {Changed style of the edit instructions
              to match surrounding edits in 6.9.}

J3/11-250   - Edits for GB43. {Done}

J3/11-253 - Edits for GB51. {Changed the subclause title "Example of
            the mapping..." to "Mapping" to match the style of other
            subclauses.}

J3/11-254   - Edits for GB44. {Done}

J3/11-251r1 - Edits for DIN4. {In the first edit, inserted missing
              comma. In the second edit, inserted reference to the
              Fortran standard to match style of the existing
              paragraphs.  Changed the style of the edit instructions
              to match the existing edits in 6.9.  Moved the last edit
              to be before the edit to move 2.4.2 to 15.6.4.}

Paper 11-249r1 contains a reply to DIN1, but no edits.

Paper 11-245r1 contains a reply to DIN3, but no edits.

----------------------------------------------------

Part 2: Changes to conform to ISO rules.

J3/11-237   - Edits to renumber the Clauses. {Added edit to update the
              list of Clauses in the Introduction.}

J3/11-242r1 - Edits to convert the Technical Report in N1869 to a
              Technical Specification.


--------------------------------------------------------

Part 3: Other edits.

J3/11-243r1 - Request from the Fortran standard editor to replace
              "points to" and "pointed to by" with terminology more
              consistent with the Fortran standard.{Edit for 5.3.5.1
              superseded by edit in J3/11-232r1.  Edit for 5.3.5.8,
              para source superseded by J3/11-234r2.}  {Missing edit
              added: 5.3.7, para 2, line 1: Change "that is pointed to
              by" to "whose address is".}

J3/11-246 - Discussion regarding whether VOLATILE is relevant to
              Restrictions on Lifetimes (5.3.7). {Added to the first
              edit: change "does not have any of ... attributes" to
              "does not have either ... attribute".}

{In 1.1 Scope, insert comma after "maintainability".}

{In 5.3.5.7, para following the strides para, delete the final
sentence "The value of result->rank ... strides that are zero.".  GB22
moved this requirement into the result para, so this sentence is now
redundant.}

{In the subclause 6.9 edits for 15.2.3.3 and 15.2.3.6, insert the name
of the subclause affected.}

{In clause 6 the subclause headings are inconsistently worded either
"Edits to xxx" or "Edits for xxx". Changed the "for" cases to "to".}

{In Annex A, the subclause headings are inconsistently worded.  Some
begin with "Example for..." or "Example of..." whereas most omit these
leading words. Delete the "Example..." wording in the cases where it
appears.}