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,df5a27b6159d7882
X-Google-Attributes: gid103376,public
From: smoore@chowgar.demon.co.uk (Simon Moore)
Subject: Re: Strange problem in GNAT 3.04 Win 95
Date: 1996/10/25
Message-ID: <3270d4ca.2656680@news.demon.co.uk>#1/1
X-Deja-AN: 191994785
x-nntp-posting-host: chowgar.demon.co.uk
references: <32707cd0.8077937@news.demon.co.uk>
 <54ocn1$604@infosrv.rz.unibw-muenchen.de>
content-type: text/plain; charset=us-ascii
organization: j%nki~w�RJ3M-26XPLZ8L-BFGD44CT-1EA6BC82
mime-version: 1.0
newsgroups: comp.lang.ada
Date: 1996-10-25T00:00:00+00:00
List-Id: <comp.lang.ada>


On 24 Oct 1996 18:32:01 GMT, e81bnick@kommsrv.rz.unibw-muenchen.de
(Nicolay Belofastow) wrote:

>I am novice in Ada, but from my C experience I know, that sometimes
>after usage of scanf function to make a formatted input (e.g. integer
>value, as you do) some extra character remains in the keyboard
> and following getchar (getc in Ada) eats it and so makes no expected
> input. 
>
> May be GNAT compiler uses inside of  the I/O package
> this C functinality. I see only  one way to overcome 
> the problem -- the same, you did -- 
> use extra getc call after the integet input.
>
> Best regards, Nick.
>--
>-------------------------------------------------
>Nickolay Belofastow
>University of the Federal Armed Forces, Munich
>e81bnick@rz.unibw-muenchen.de

Hi Nick

Thanks for the reply, I guess I'll have to live with the problem.

Regards.

*****************************************************************************
* Simon Moore - smoore@chowgar.demon.co.uk - http://www.chowgar.demon.co.uk *
*****************************************************************************