From owner-sc22wg5@dkuug.dk Fri Jul 25 09:45:17 2003 Received: (from majordom@localhost) by dkuug.dk (8.12.8p1/8.9.2) id h6P7jHi8025951 for sc22wg5-domo; Fri, 25 Jul 2003 09:45:17 +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 srv1.pamela.getrealnet.net (pamela.getrealnet.net [212.90.32.71]) by dkuug.dk (8.12.8p1/8.9.2) with ESMTP id h6P7ifEc025943 for ; Fri, 25 Jul 2003 09:45:13 +0200 (CEST) (envelope-from dmuxworthy1@justdial.it) Received: from [212.90.36.134] (helo=David-Muxworthys-Computer.local.) by srv1.pamela.getrealnet.net with esmtp (Exim 3.35 #3) id 19fxHa-0008LN-00 for sc22wg5@dkuug.dk; Fri, 25 Jul 2003 08:46:30 +0100 Date: Fri, 25 Jul 2003 08:36:36 +0100 Reply-To: d.muxworthy@bcs.org.uk Subject: Paper N1547 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v543) From: David Muxworthy To: sc22wg5@dkuug.dk Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: Apple Mail (2.543) Sender: owner-sc22wg5@dkuug.dk Precedence: bulk ISO/IEC JTC1/SC22/WG5 N1547 Miscellaneous minor edits to 03-007 David Muxworthy This is a revision of the proposed edits which were distributed in SC22WG5 e-mail message 2893 of July 24 2003. Thanks are due to Malcolm Cohen for suggesting corrections and improvements. 1. May not ISO (and BSI) style rules do not allow use of "may not" to express a prohibition because it is ambiguous. It could mean "must (or can) not", or "it might not happen that" or "is not permitted to". The following edits would remove the phrase. 34:13 "may not" -> "shall not" 41:0+5 "may not" -> "might not" 59:8+3 "may not" -> "cannot" 176:4+2 "may not" -> "cannot" 176:37 "may or may not" -> "might or might not" 194:12+3 "may not" -> "shall not" 245:5+3 "may not" -> "shall not" 249:7+3 "may not" -> "might not" 312:8+9 "may or may not" -> "might or might not" 467:35 "may or may not" -> "might or might not" 467:32 "may or may not" -> "might or might not" 469:24 "may or may not" -> "might or might not" 469:28 "may or may not" -> "might or might not" While on the subject, paper N1524 (referring to 03-104r2) suggests changing line 489:27 from ".. which may be unsupported..." to "... which might be unsupported...". I would suggest "... which might not be supported..." 2. Normative references Section 1.9 states that ISO/IEC 646:1991 is to be referenced herein as "the ASCII standard" and ISO/IEC 9899:1999 as "the C standard". There is no such shorthand for ISO/IEC 10646-1:2000 which is referenced in full some half dozen times. Is this deliberate or an oversight? In any case the first short form is not used consistently. "ASCII standard" is used only once, at 42:12, whereas the full form is used at 40:12 and 322:1-2. I would suggest replacing the latter two by the short form. The term "C standard" is used multiple times. 3. Other edits 8:29 "9989" -> "9899" {we ought to get the reference to the C standard right} 182:13 "do not do" -> "do not perform" {we usually "perform" I/O rather than "do" it}