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

[David A. Wheeler]

Andy Wingo:

> So, we are repeating ourselves here :)  I agree with you but I can't see
> a good way of implementing this.

Would the per-port reader options be reasonable place to store the info
about EOF?

--- David A. Wheeler