From owner-sc22wg5@dkuug.dk Thu Sep 4 21:52:58 2003 Received: (from majordom@localhost) by dkuug.dk (8.12.8p1/8.9.2) id h84Jqwhb019392 for sc22wg5-domo; Thu, 4 Sep 2003 21:52:58 +0200 (CEST) (envelope-from owner-sc22wg5@dkuug.dk) X-Authentication-Warning: ptah.dkuug.dk: majordom set sender to owner-sc22wg5@dkuug.dk using -f Received: from mtiwmhc11.worldnet.att.net (mtiwmhc11.worldnet.att.net [204.127.131.115]) by dkuug.dk (8.12.8p1/8.9.2) with ESMTP id h84JqnCp019382 for ; Thu, 4 Sep 2003 21:52:53 +0200 (CEST) (envelope-from dick.hendrickson@att.net) Received: from att.net (49.minneapolis-10rh15rt.mn.dial-access.att.net[12.82.82.49]) by mtiwmhc11.worldnet.att.net (mtiwmhc11) with SMTP id <2003090419524911100mr3que>; Thu, 4 Sep 2003 19:52:50 +0000 Message-ID: <3F57998A.CC597F12@att.net> Date: Thu, 04 Sep 2003 14:59:06 -0500 From: Dick Hendrickson X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "sc22wg5@dkuug.dk" Subject: Re: (SC22WG5.2970) Paragraph numbers References: <200309041843.h84IhXMm018889@dkuug.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-sc22wg5@dkuug.dk Precedence: bulk Van.Snyder@jpl.nasa.gov wrote: > > Bill Long wrote: > > > Adding paragraph > > numbers would be a redundant location scheme that invites notation > > confusion - what does [132:2] mean? It might, but if we eliminate line numbers we define away the redundancy ;-). Seriously, in the old days it was a pain to try and process a paper from a previous**n meeting; getting the new page/line numbers was just hard. If Richard can find a way to permanently attach the paragraph number to the text I think it will be much easier to work on F2020. I think the first few working meetings on the next standard will have tons of semi-draft papers that will get updated for each meeting. Having to also redo line numbers as things get approved is hard. Permanent numbers will also make it easier to fit F2003 interps into the next Fortran. > > This is easily overcome by agreeing to a different notation for > page/paragraph/line-in-paragraph as opposed to page/line. How about > [132.2] for page 132 paragraph 2, [132.2:5] for line 5 of paragraph > 2 on page 132, and [132:2] for page 132 line 2? The extensions to ranges > are obvious. > The trouble with this is that people will confuse the distinction between [123.4] and [123:4]. Wasn't there a C interp that hinged on whether or not a comma was set in italic font? This looks like the same trap to me. If we get in the habit of saying something like "change the sentence in para 123 (4th line) that begins 'An executable...' to 'A non-executable...'" it's a lot easier for people to follow the edits. Dick Hendrickson > Another possibility is to qualify paragraph numbers fully by their subclause > number, so [132.2] would be 7.1.8.6.2, or maybe something like 7.1.8.6/2 > to make it clear that 7.1.8.6.2 is not going to be found on a subclause > heading. > > -- > Van Snyder | What fraction of Americans believe > Van.Snyder@jpl.nasa.gov | Wrestling is real and NASA is fake? > Any alleged opinions are my own and have not been approved or disapproved > by JPL, CalTech, NASA, Sean O'Keefe, George Bush, the Pope, or anybody else.