From jkr@jkr.cc.rl.ac.uk Thu Jul 20 14:53:39 2000 Received: from nameserv.rl.ac.uk (nameserv.rl.ac.uk [130.246.135.129]) by dkuug.dk (8.9.2/8.9.2) with ESMTP id OAA83951 for ; Thu, 20 Jul 2000 14:53:39 +0200 (CEST) (envelope-from jkr@jkr.cc.rl.ac.uk) Received: from jkr.cc.rl.ac.uk (jkr.cc.rl.ac.uk [130.246.8.20]) by nameserv.rl.ac.uk (8.8.8/8.8.8) with ESMTP id NAA09457 for ; Thu, 20 Jul 2000 13:53:38 +0100 Received: (from jkr@localhost) by jkr.cc.rl.ac.uk (8.8.8+Sun/8.8.8) id NAA17140 for SC22WG5@dkuug.dk; Thu, 20 Jul 2000 13:54:45 +0100 (BST) Date: Thu, 20 Jul 2000 13:54:45 +0100 (BST) From: John Reid Message-Id: <200007201254.NAA17140@jkr.cc.rl.ac.uk> To: SC22WG5@dkuug.dk Subject: N1387 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" ISO/IEC JTC1/SC22/WG5 N1387 To: WG5 From: Japanese Fortran committee Date: July 14, 2000 Subject: Part 3 Defect Items Japanese Fortran Committee found the following defect items of ISO/ISE 1539-3 during the translating work. ----------No.JP-1---------------------------------------------------- NUMBER: JP-1 TITLE: The term "coco" is missing KEYWORD: coco DEFECT TYPE: STATUS: QUESTION: The term "coco" is missing from some descriptions. Followings are samples of missing "coco", - 3.1, line 33 "a character literal" should be "a coco character literal". - 3.2, line 8 "Each token is a keyword, a name, a literal constant, an operator (see Table 2), ..." should be "Each token is a coco keyword, a name, a coco literal constant, an operator (see Table 2), ..." - 9, line 16 "A named constant declared ... as a constant with ..." should be "A coco named constant declared ... as a coco constant with". - 9, line 18 "in its type declaration directive" should be "in its coco type declaration directive". - 9, Note 9.4, line 3 "those variables that" should be "those coco variables that". ANSWER: EDIT: SUBMITTED BY: HISTORY: ----------No.JP-2---------------------------------------------------- NUMBER: JP-2 TITLE: A character literal is not a part of literal constant KEYWORD: character, constant, literal DEFECT TYPE: STATUS: QUESTION: 3.2, line 8 to 9 states that : "Each token is a keyword, a name, a literal constant, an operator (see Table 2), a comma,..." In this list of tokens, "a coco character literal" is missing. A character literal is not included in a literal constant. ANSWER: EDIT: SUBMITTED BY: HISTORY: ----------No.JP-3---------------------------------------------------- NUMBER: JP-3 TITLE: A sequence of blank characters in a coco line KEYWORD: blank, character, literal DEFECT TYPE: STATUS: QUESTION: 3.2, line 12 to 13 states that : "A sequence of blank characters outside of a coco character literal is equivalent to a single blank character." This description is about the blank characters in a coco line. The phrase "in a coco line" should be attached like : "In a coco line, a sequence of blank characters outside of a coco character literal is equivalent to a single blank character." ANSWER: EDIT: SUBMITTED BY: HISTORY: ----------No. JP-4---------------------------------------------------- NUMBER: JP-4 TITLE: Continuation of comment KEYWORD: comment, continuation, line DEFECT TYPE: STATUS: QUESTION: 3.2.2, line 2 states that : "Coco comment lines shall not be continued; an "&" in a coco comment has no effect during coco execution." Not only a coco comment line but also a coco comment shall not be continued. This description should be : "Coco comments shall not be continued; an "&" in a coco comment has no effect during coco execution." ANSWER: EDIT: SUBMITTED BY: HISTORY: ----------No.JP-5---------------------------------------------------- NUMBER: JP-5 TITLE: Coco variable becomes defined by the SET file KEYWORD: defined, initial value, SET file, variable DEFECT TYPE: STATUS: QUESTION: 8.2 states the events that cause coco variables to become defined. But the description about the SET file is missing. The following should be included after (2) of 8.2 : "(3) Beginning of execution of a coco program causes variables initialized in the SET file to become defined with those initial value." ANSWER: EDIT: SUBMITTED BY: HISTORY: ----------No.JP-6---------------------------------------------------- NUMBER: JP-6 TITLE: Declaration in SET file and coco program KEYWORD: declaration, SET file, variable DEFECT TYPE: STATUS: QUESTION: 9, line 19, second constraint states that : "A coco variable declared in the coco-set-file shall be given an initial value in its type declaration directive and shall be declared with the same type in an executed coco directive in the coco program." The phrase "as a coco variable" should be inserted before "with the same type ..." as follows : "A coco variable declared in the coco-set-file shall be given an initial value in its type declaration directive and shall be declared as a coco variable with the same type in an executed coco directive in the coco program." ANSWER: EDIT: SUBMITTED BY: HISTORY: ----------No.JP-7---------------------------------------------------- NUMBER: JP-7 TITLE: Missing line KEYWORD: coco-alter-directive, shift DEFECT TYPE: STATUS: QUESTION: In the chapter 9, there is no description about the behaviour without coco-alter-directive. The following statement contained in FDIS is missing just before the Note 9.1 : "If there is no coco-alter-directive, the behaviour is as for SHIFT3." ANSWER: EDIT: SUBMITTED BY: HISTORY: ----------No.JP-8---------------------------------------------------- NUMBER: JP-8 TITLE: The term "coco object" is undefined KEYWORD: coco object DEFECT TYPE: STATUS: QUESTION: 9, Note 9.4, line 3 to 5 states that : "For instance, if a name is misspelled in the SET file, this will be diagnosed by the system unless the misspelled name happens to be that of another coco object with matching properties." The term "coco object" is not defined in this standard. ANSWER: EDIT: SUBMITTED BY: HISTORY: ----------END-------------------------------------------------------