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,e89e4fc8b5c5f198
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: get_line
Date: 1998/06/06
Message-ID: <dewar.897143686@merv>#1/1
X-Deja-AN: 360140041
References: <Pine.OSF.3.95.980605111447.22858A-100000@esus.cs.montana.edu>
 <6lbg7h$nnv$1@goanna.cs.rmit.edu.au>
X-Complaints-To: usenet@news.nyu.edu
X-Trace: news.nyu.edu 897143787 6978 (None) 128.122.140.58
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1998-06-06T00:00:00+00:00
List-Id: <comp.lang.ada>


Dale said

<<The solution is to read the characters in char by char. It is
unfortunate that Get_Line has such a weak postcondition.
>>

By far the best programming technique here is to read the line into a giant
buffer that is sure to be long enough, and then program what you want done
with the string depending on the length.

Reading it in directly as in the original program is clearly bad practice,
since it leaves undefined junk if the string is too short.