08-243r1 To: J3 From: Van Snyder, originally from Michael Ingrassia Subject: Public Comment J32029 Date: 2008 August 14 ---------------------------------------------------------------------- Commenter: Robert Corbett Subject: "Fix error in type equivalence" Paragraph 2 of Section 4.5.1.3 states Data entities in different scoping units also have the same type if they are declared with reference to different derived-type definitions that specify the same type name, ... Why should it matter that that the data entities are in different scoping units? Shouldn't the same rules apply if the data entities are in the same scoping unit? The answer to the first question is that it should not matter, and the answer to the second is that the same rules should apply. Examination of the first paragraph of Section 4.5.3.1 reveals what likely happened. That paragraph states Derived-type definitions with the same name may appear in different scoping units, in which case they may be independent and describe different derived types or they may describe the same type. Obviously, the phrase "in different scoping units" in the quotation from paragraph 2 was misapplied to the data entity. It should have been applied to the derived-types definitions. ---------------------------------------------------------------------- J3 response: J3 agrees that there is a problem, but it is in 4.5.2.4p2 (there is no subclause 4.5.1.3, and 4.5.3.1 does not have a paragraph similar to the cited one). [61:4.5.2.4p2] Editor: After "Data entities" delete "in different scoping units".