From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=0.8 required=3.0 tests=BAYES_50,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.5-pre1
X-Received: by 2002:a05:622a:42:: with SMTP id y2mr12055330qtw.186.1611788957337;
        Wed, 27 Jan 2021 15:09:17 -0800 (PST)
X-Received: by 2002:a25:9902:: with SMTP id z2mr17987705ybn.339.1611788957208;
 Wed, 27 Jan 2021 15:09:17 -0800 (PST)
Path: eternal-september.org!reader02.eternal-september.org!news.mixmin.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Wed, 27 Jan 2021 15:09:17 -0800 (PST)
In-Reply-To: <5af60c88-b7ab-4849-badb-c407823d45e0n@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: google-groups.googlegroups.com; posting-host=146.5.2.231; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC
NNTP-Posting-Host: 146.5.2.231
References: <5af60c88-b7ab-4849-badb-c407823d45e0n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <05057da7-40d1-46f4-9a95-531c746cb556n@googlegroups.com>
Subject: Re: Problem with unbounded string input
From: Shark8 <onewingedshark@gmail.com>
Injection-Date: Wed, 27 Jan 2021 23:09:17 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: reader02.eternal-september.org comp.lang.ada:61226
List-Id: <comp.lang.ada>

On Wednesday, January 27, 2021 at 12:59:18 PM UTC-7, Brian McGuinness wrote=
:
> I was having trouble reading unbounded strings, so I wrote a short test p=
rogram and had the same problem.=20
>=20
>=20
> When I compile this with gnatmake 8.3.0 under Linux Mint Debian edition 4=
 and run it, every so often when I type a line and hit Enter there is no re=
sponse until I hit Enter again, and then everything typed before the first =
Enter is ignored. The rest of the time the lines I type are read and return=
ed correctly. I am really puzzled by this. Is this a bug in the Ada library=
 or am I doing something wrong?=20

I've had this problem before, though it was using normal strings; IIRC the =
issue is that sometimes there's "stuff" in your input buffer and this can b=
e handled [IIRC] via flush.