From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,87a926dbf0cf8cb1 X-Google-Attributes: gid103376,public From: Marin David Condic Subject: Re: newbie problem Date: 1998/12/04 Message-ID: <3668037A.F6C05CA2@pwfl.com>#1/1 X-Deja-AN: 418643965 Content-Transfer-Encoding: 7bit Sender: condicma@nameserver.pwfl.com References: <3667EE11.6E94BA0F@interact.net.au> <748rsl$2jv@gcsin3.geccs.gecm.com> To: Simon Bracken Content-Type: text/plain; charset=us-ascii Organization: Pratt & Whitney Mime-Version: 1.0 Reply-To: diespammer@pwfl.com Newsgroups: comp.lang.ada Date: 1998-12-04T00:00:00+00:00 List-Id: Simon Bracken wrote: > > > with Text_IO; > procedure Example is > > subtype TEXT_STRING is STRING (1 .. 80); > type VARYING is > record > Text : TEXT_STRING; > Last : NATURAL; > end record; > > Input_Record : VARYING; > You'll want to notice that you are basically duplicating the Bounded_String type found in the package Ada.Strings.Bounded. (ARM A.4.4) Wherever possible, IMHO, its best to use the data types & operators supplied by the language rather than reinvent the wheel. Of course, you do have the problem I observed in a related post in that Text_IO will only deal directly with the standard type String. MDC -- Marin D. Condic Real Time & Embedded Systems, Propulsion Systems Analysis United Technologies, Pratt & Whitney, Large Military Engines M/S 731-95, P.O.B. 109600, West Palm Beach, FL, 33410-9600 Ph: 561.796.8997 Fx: 561.796.4669 "The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." -- G.B. Shaw