Subject: bug#10491: unread-char and eof

From: Aleix Conchillo Flaqué <[email-masked]>
Date: Thu, 12 Jan 2012 12:14:04 -0800

Whenever eof is reach in a port, a call to unread-char passing eof
triggers an error. I'm not sure what's the right behavior for this,
but I guess the way it is now is just as the user should be
responsible to check eof.

A note in the documentation would help in any case.