io.Reader documentation states that a
Read() may return a non zero
n value and an
io.EOF at the same time. Unfortunately, the
Read() method of a
File doesn't do that.
When the EOF is reached and some bytes could still be read, the Read method of file returns non zero
nil error. It is only when we try to read when already at the end of the file that we get back zero
io.EOF as error.
I couldn't find a simple method to test if the EOF is reached without trying to read data from the file. If we perform a Read() with a buffer of 0 byte, we get back zero
nil error although we are at the end of file.
To avoid this last read, the only solution I have found is to keep track myself of the number of bytes remaining to read in the file. Is there a simpler solution ?