Re: [Bug-ed] Removed funny behavior on EOF

[Antonio Diaz Diaz]

This is the same change I planned to do. :-)


Andrea Monaco wrote:
> + /* when possible, it's better to put a null character */
> +        if( bufsz > i ) buf[i] = 0; if( sizep ) *sizep = i;

"resize_buffer" can be moved to the top of the loop so that it is always 
possible to put a null character.

OTOH, I read this in the glibc manual:

"Most errors that can happen are not recoverable -- a second try will
always fail again in the same way.  So usually it is best to give up and
report the error to the user, rather than install complicated recovery
logic.

   One important exception is `EINTR' (*note Interrupted Primitives::).
Many stream I/O implementations will treat it as an ordinary error,
which can be quite inconvenient.  You can avoid this hassle by
installing all signals with the `SA_RESTART' flag."


So maybe the "double EOF" is there to handle an interrupted "getchar", 
in which case we should leave it alone.


Regards,
Antonio.