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,5d47c120235ba244 X-Google-Attributes: gid103376,public From: mheaney@ni.net (Matthew Heaney) Subject: Re: Text_IO.Get_Line Date: 1997/05/19 Message-ID: #1/1 X-Deja-AN: 242499297 References: <19970519224400.SAA06280@ladder02.news.aol.com> Organization: Estormza Software Newsgroups: comp.lang.ada Date: 1997-05-19T00:00:00+00:00 List-Id: In article <19970519224400.SAA06280@ladder02.news.aol.com>, rehixon@aol.com (RE Hixon) wrote: >Thanks for your reply concerning Get_Line. In MASM 6.1, when I request a >buffered string input, the system will only allow the user to enter the >maximum number of characters that I have allowed to be stored in memory. >If the user trys to enter more than what I have declared, the system will >beep and not allow any more input. I would like to duplicate this using >Ada 95. But the point is that that doesn't necessarily need to be a restriction. It's a restriction because you have made the choice that it be a restriction. As shown in the previous post, using a loop to read all the line, and appending each segment to an unbounded_string, means the restriction need not be there. Of course, you may have other reasons for the restriction, but "size of the internal buffer" doesn't need to be one. -------------------------------------------------------------------- Matthew Heaney Software Development Consultant (818) 985-1271