bug#12216: peek-char incorrectly *CONSUMES* eof

[David A. Wheeler]

On Thu, 14 Mar 2013 13:13:39 -0400, Mark H Weaver <address@hidden> wrote:
> One extra check per read primitive is hardly enough of a cost to
> consider abandoning correctness, IMO.

Though I've not reviewed this code, I *think* you'd only need to check when the 
buffer is empty.  When the buffer is empty, it'll take a while for the OS to 
fill it anyway, far more than checking a boolean value.

--- David A. Wheeler