Re: End_Of_File does not work as expected...

[Jeff Carter <jrcarter@acm.org>]

Mika Fischer wrote:
> All I can see is this:
> 
> | function End_Of_File return Boolean;
> |
> | (25)
> |      Operates on a file of mode In_File. Returns True if a file
> |      terminator is next, or if the combination of a line, a page, and a
> |      file terminator is next; otherwise returns False.
> 
> which doesn't explain why that does not work in my program.

Thus we can see that two line terminators at the end of the file will
result in End_Of_File being False. The description of Get (Character)
explains why it will raise End_Error in this situation.

[concerning input from the console:]
> Yeah, well. But if I read one character at once I would expect it to look
> like this:
> --<snip>--
> dddddd
> 
> --<snip>--
> 
> Or has this got something to do with buffered output? I'll look this up.

Get will probably wait for an entire line of input to be read and echoed
by the OS before reading a character. If you need immediate input, you
should probably be looking at Get_Immediate.

-- 
Jeff Carter
"Now go away or I shall taunt you a second time."
Monty Python & the Holy Grail