ISO IEC/JTC 1/SC 22/WG5/N1827
To: J3/WG5
From: Malcolm Cohen
Subject: Editor's report on WG5 pre-DIS ballot
Date: 2010/04/20


1. Introduction
---------------

This report describes the changes between N1814 and N1826, in terms of
the comments received during the recent WG5 ballot.  Section 3 describes
the results of a quick post-processing review.


2. Ballot comments and responses.
---------------------------------

Cohen 1
  Introduction, page xiv, "Programs and procedures:" bullet point,
   after "A null pointer" insert "or unallocated allocatable".
Done.

Cohen 2
  10.10.4 "List-directed output", paragraph 13 (page 266),
  after "Except for"
  insert "new records created by explicit formatting within a defined
          output procedure or by"
Done.
Also changed "may be"->"is" in Notes 10.33 (page 266) and 10.39 (page 270).

Cohen 3
 Introduction, page xii, bullet-point "Execution control:",
 append new sentence to paragraph:
   "The ERROR STOP statement initiates error termination."
Done.

Long 1
  In Note 8.45 (page 194 in 8.5.6 LOCK and UNLOCK statements) replace the
  first comment in the example code:
     ! Lock to manage the work queue
  with
     ! Lock on each image to manage its work queue
Done.

Muxworthy 1
  There are bad page breaks at the bottom of pages 52, 380 and 565.
52 - fixed.
380 - fixed.
565 - risked a change to j3.cls to fix this, seems to have worked with
      no ill effects.

Muxworthy 2  
  Similarly on pages 151, 486, 492, 522 but of much lower, possibly
  negligible, priority.
151 - I disagree that this is a bad page break; this is all one sentence,
      it has 14 lines on page 151 and 15 lines on page 152.  I see no
      significantly better split - the most obvious candidate to avoid
      ending the page on a disjunction would be the beginning of item (4) 5
      lines earlier, and this would look horrible.  In fact ending the page
      on a disjunction is good, since it makes the reader turn the page to
      see the rest of the list.
      However, there is a spurious paragraph number in the middle of the
      sentence, viz after the list - fixed.
486 - fixed.
492 - substantially reset C.7.2 with j3.cls macro changes.  I gave the
      "Example" subheadings paragraph numbers, took the paragraph numbers
      off the code and file contents listings, indented the code and file
      contents listings.
522 - I made some changes to fix this, but the problem has moved away
      anyway due to other changes.
Also noticed C.6.2 (page 488) had many spurious paragraph numbers:
fixed by resetting that subclause and indenting the examples.

Muxworthy 3
  Table 2.1, split between pages 31 and 32, is not well presented; it
  was not so split in F95 or F03.  This could be resolved by additional
  white space on pages 30 and 31 or by interchanging subclauses 2.3.2
  and 2.3.3.
Deleted spurious subheading "2.2.3.1 General".
Removed extraneous line in Table 2.1 that appeared when it was broken
across pages.
Moved table 2.1 to the beginning of subclause 2.3.2 so that it is no
longer split across pages.

Muxworthy 4  
  The diagram of the plasma module would be improved if it were not split
  over two pages (504 & 505).  Also it should now use continuous lines
  rather than ASCII characters.
I have turned this into a table instead.

Reid 1
  The N number for the DIS is N1826.
Done.
Also changed date to 2010-04-20,
and on the cover page, "for WG5 ballot"->"for ballot".

Snyder 1
  In 13.7.136p3, p380, insert "a" before "default" in the description of
  the SIZE argument.
Done.

Snyder 2
  In 13.7.136p3, p380, insert a full stop after "N" in the description of
  the GET argument.
Done.

Xia 1 (this comment was after the deadline)
  references to <notify-stmt> and <query-stmt> in D.2 ... should be
  removed.
Done.


3. Post-processing review
-------------------------

(1) While looking for bad page breaks, I notice poorly placed paragraph
    numbers in C.11.3, viz on the code not on the subheadings; it's
    arguable, but things like "2 struct pass {" look particularly bad.
    Maybe the subheadings should not have paragraph numbers either, but
    the sample code should definitely not.
Reset C.11.3 to make it look nicer and take slightly less space thus
fixing the bad page break 3 pages later.

(2) [45:3.3.2.2p3] spotted END MODULE and END INTERFACE swapped in table.
Fixed.

(3) Some suboptimal page breaks noticed: it is probably not worth trying to
    fix these:
    p68, p72, p95, p120, p124, p156, p164, p171, p174, p202, p206, p220.
    Note: this list is not exhaustive.
No action taken.

(4) Note 5.42 uses ASCII art, but then EQUIVALENCE is old and cruddy.
No action taken.

(5) xiv, "Programs and procedures", second sentence needs "target" after
    "procedure pointer".
Fixed.

(6) [275:11.2.3p2] "descendents"->"descendants".
Fixed.

(7) [316:13.2.4 heading] "Dim arguments"->"DIM arguments"
    (they don't suffer from reduced light levels).
Fixed.

(8) [269:Note 10.38] There was a very bad page break as a knock-on effect
    of the change (Cohen 2) on page 266.
Joined two lines of code together to fix the page break.

===END===
</div>