VHDL Issue Number: 0123 Classification: Language Inconsistency Language Version: VHDL-87 Summary: The READ procedures for unconstrained array types BIT_VECTOR and STRING in package TEXTIO should return a LENGTH parameter, for the same reason that the READ procedure in general returns this parameter. Related Issues: ??? Relevant LRM Sections: 14.3, 3.4.1 Key Words and Phrases: File I/O, Package TEXTIO, Unconstrained Arrays Current Status: Submitted 1076-1993 Disposition: Bugs Fixed, Enhancements Outstanding (No ISAC Issues) Disposition Rationale: Non-ISAC issues outstanding. 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: N/A ----------------------- Date Analyzed: TBD Author of Analysis: TBD Revision Number: $Revision: 1.9 $ Date Last Revised: $Date: 1995/08/04 01:36:30 $ Description of Problem ---------------------- The final issue is not really an error, but more of an inconsistency. The predefined READ procedures for BIT\_VECTOR and STRING in package TEXTIO (chapter 14.3) return a VALUE but not a LENGTH. The READ procedure which gets defined whenever you declare some file type whose base is an unconstrained array always returns a LENGTH. (see chapter 3.4.1) This is so you can tell exactly how many elements of that unconstrained type actually got returned. Proposed Resolution ------------------- It would be more consistent if the predefined READ procedures defined in package TEXTIO for the predefined unconstrained array types BIT\_VECTOR and STRING would also return such a parameter. VASG-ISAC Analysis & Rationale ------------------------------ VASG-ISAC Recommendation for IEEE Std 1076-1987 ----------------------------------------------- VASG-ISAC Recommendation for Future Revisions ---------------------------------------------