VHDL Issue Number: 0124 Classification: Language Definition Problem Language Version: VHDL-87 Summary: Conflicting passages from the LRM about limitations on the designated type of an access type. Related Issues: Relevant LRM Sections: 3.3.1, 3.3 Key Words and Phrases: Access types, Designated type of an access type, File Types Current Status: ISAC-Approved 1076-1993 Disposition: Closed Disposition Rationale: Section 3.3.1 changed Superseded By: N/A ----------------------- Date Submitted: 1989/06/21 Author of Submission: Ken Scott Author's Affiliation: Vantage Analysis Systems, Inc. Author's Post Address: 42840 Christy St., Suite 201 Fremont, CA 94538 Author's Phone Number: (415) 659-0901 Author's Fax Number: Author's Net Address: ----------------------- Date Analyzed: 1990/10/02 Author of Analysis: Doug Dunlop Revision Number: $Revision: 1.6 $ Date Last Revised: $Date: 1995/05/13 21:53:48 $ Description of Problem ---------------------- The first line of Section 3.3.1 states that: "There are no particular limitations on the designated type of an access type." To contradict this, the last sentence of the 2nd paragraph of Section 3.3 states that: "The designated type [of an access type] must not be a file type." This seems to be a contradiction. Rewording the former of these two sentences would probably help clarify this inconsistency. Proposed Resolution ------------------- Reword the first sentence or eliminate it entirely. VASG-ISAC Analysis & Rationale ------------------------------ The quoted sentence from LRM 3.3.1 is misleading. It is introductory in nature and does not add any correct information. VASG-ISAC Recommendation for IEEE Std 1076-1987 ----------------------------------------------- The ISAC suggests readers either ignore this sentence or read it as though it were written: "Other than the restriction that the designated type of an access type may not be a file type (see Section 3.3), there are no additional limitations on the designated type of an access type." VASG-ISAC Recommendation for Future Revisions --------------------------------------------- Repair this problem in the wording of the LRM.