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=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!rex!ames!ads.com!bhanafee
From: bhanafee@ADS.COM (Brian Hanafee)
Newsgroups: comp.lang.ada
Subject: Re: Design/Development questions
Message-ID: <NT{$9S%@ads.com>
Date: 8 Jun 90 20:22:04 GMT
References: <677@tfsg.UUCP> <67999@cc.utah.edu>
Sender: usenet@ads.com (USENET News)
Organization: Advanced Decision Systems, Mt. View, CA (415) 960-7300
List-Id: <comp.lang.ada>

In article <67999@cc.utah.edu> RCAPENER@cc.utah.edu writes:
[stuff on a different topic deleted]

>In VAX-Ada, the GET and the GET_LINE procedures have the very
>disconcerting behavior that when you get a string, you must enter
>the EXACT number of characters the string is declared for.  Is this
>behavior part of the LRM?  Does anyone in NetLand have the equivalent
>of C's fgets for strings in Ada?  Any input (pun intended) on solving
>this problem will be appreciated.

As I (not a lawyer) interpret this, the behavior is correct for Get,
but incorrect for Get_Line.  The sections of the LRM I'm looking at
are 14.3.6/9 and 14.3.6/13. (If you're talking about some other
version of Get, then ignore this; this is the version to Get strings
from files).
14.3.6/9 states (for Get):
	"Determines the length of the given string and attempts that
	number of GET operations for successive characters of the
	string (in particular, no operation is performed if the string
	is null)."

14.3.6/13 states (for Get_Line):
	"...Reading stops if the end of the line is met...reading also
	stops if the end of the string is met.  Characters not
	replaced are left undefined."

Brian