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,eee47022b0e39dbb
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Exception problem
Date: 1997/02/19
Message-ID: <dewar.856364227@merv>#1/1
X-Deja-AN: 219861362
References: <330A0D25.313@fs2.assist.uci.edu>
 <01bc1e5e$a43929a0$148c71a5@dhoossr.iquest.com>
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-02-19T00:00:00+00:00
List-Id: <comp.lang.ada>


David said

<<The problem is that when Text_IO.Data_Error is raised in this circumstance,
the pointer in the input stream is backed up to where it was before the
Int_IO.Get was called>>

A clearer and more accurate (though equivalent) is that the pointer in the
input stream is never moved past the bad character in the first place, so
no backing up is needed, i.e. the pointer is moved to the first non-blank,
and then is only moved further if valid input is found.