just for fun: pop quiz

[Peter Haworth]

I ran into this a few weeks ago when I was having problems reading a file.
 Turned out it was because I should have been doing a binary read, but
seeing EOF in the result made me think I'd run into some sort of error like
an unexpected EOF or something - wasted a couple of hours trying to track
that down.

On Sun, Feb 3, 2013 at 11:08 AM, Richard Gaskin
<ambassador at fourthworld.com>wrote:

> It's been around so long that they're not likely to change it, so I won't
> be littering the RQCC with yet another unactionable request.
>
> Still, does seem odd.
>
> Can you think of a circumstance in which you've already specified to read
> until EOF, and the command executes flawlessly just as you've asked it to,
> yet you still need to be notified that it reached EOF?
>



Pete
lcSQL Software <http://www.lcsql.com>