Re: Weird string I/O problem

[Jean-Pierre Rosen <rosen@adalog.fr>]

Jerry a �crit :

> So my problem is solved, but I'm still puzzled. All I'm trying to is
> to very simple IO from keyboard and monitor to enter e.g. a numeric
> parameter into my program as well as, say, a file name. So any Get on
> a Float followed by any of the Get_Line routines will raise this
> problem. It just seems odd to me that for such a simple application, I
> have to remember to clear the dangling line terminator after  the Get
> on a Float. (Or, in the present case, since I have easy access to the
> code, to have the Get_Line do it for me.)
> 
The real issue is that you never know what the user will type! Suppose 
you want to get a real value, and the user types:

3.14 Ooops one of my keys got stuck -------------------------------

What should you do? Clearly, the language has no opinion about this, it 
is just designed in a way that allows /you/ to implement anything you 
want. For example:

1) Ignore everything until EoL => call skip_line
2) Make it an error => write a message if End_Of_Line is false after 
reading.
3) Allow only spaces after the number => Read the remaining of the line 
with Get_Line, and do your own analysis
4) Consider that it is text for the next get of string, unless there is 
no remaining text on the same line => if end_of_line then skip_line

etc...

-- 
---------------------------------------------------------
            J-P. Rosen (rosen@adalog.fr)
Visit Adalog's web site at http://www.adalog.fr