From J.Reid@letterbox.rl.ac.uk Wed Jan 22 13:14:16 1997 Received: from letterbox.rl.ac.uk (letterbox.rl.ac.uk [130.246.8.100]) by dkuug.dk (8.6.12/8.6.12) with SMTP id NAA01475 for ; Wed, 22 Jan 1997 13:10:21 +0100 Received: from jkr.cc.rl.ac.uk by letterbox.rl.ac.uk with SMTP (PP) id ; Wed, 22 Jan 1997 12:09:36 +0000 Received: by jkr.cc.rl.ac.uk (4.1/SMI-4.1) id AA06438; Wed, 22 Jan 97 12:09:34 GMT Date: Wed, 22 Jan 97 12:09:34 GMT From: jkr@letterbox.rl.ac.uk (John Reid) Message-Id: <9701221209.AA06438@jkr.cc.rl.ac.uk> To: sc22wg5@dkuug.dk Subject: Informal Ballot on N1243 __________ I believe that the current draft is ready for | | NO | submission to SC22 for its first CD ballot |_____|____| If NO, please provide details of what changes you wish to see made in order that the document will be suitable for submission to SC22 for balloting. (signed) John Reid (date) 22/1/97 Reasons: 1. More work is needed on the typesetting (details below). 2. The SET option should not be processor dependent (detailed suggestion below). 3. I also have some minor comments. 1. Typesetting ^^^^^^^^^^^^^^ a. Add headers and footers, including page numbers. b. Use italic font for bnf terms appearing in the main text and the constraints. c. Justify the main text. d. Use bold for title of section CC3.3.3. e. Use a black square for the bnf continuation symbol. f. Indent constraints as in the standard. g. Reduce the leading in the bnf of section CC6.2.1. h. Left-aflign the text that follows the bold kewords "is" and "or" in the bnf. 2. The SET option ^^^^^^^^^^^^^^^^^ I would like to see the SET option standardized as a coco file that precedes the coco program proper. This could be done with no change to the present semantics, but I think it would be much better to have no special rules and interpret the two files as having being concatenated. This does need changes. I suggest 1. Constants be allowed to be redeclared with the same type and same value. 2. Variables be allowed to be redeclared with the same type. Any initialization is ignored if the variable is already defined. This would make a significant simplication of the present proposal as well as aiding portability. 3. Minor comments ^^^^^^^^^^^^^^^^^ a. CC3.2/-3 Delete line: "Adjacent ..." b. CC3.3 Remove all the special rules for INCLUDE and treat it as in the main standard. c. CC7. Reword. The ERROR directive causes a string to be made available. Its likely use is for the coco program detecting something wrong. The STOP directive causes coco execution to stop. Its likely use is for the coco program detecting something that it cannot handle.