[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Daniel Hartwig
Subject: bug#12216: peek-char incorrectly *CONSUMES* eof
Date: Sun, 10 Mar 2013 08:23:41 +0800

On 10 March 2013 01:11, David A. Wheeler <address@hidden> wrote:
> Daniel Hartwig:
>> and when read-char and peek-char return the former
>> value it is only to signal a _current_ lack of characters and should
>> not be considered part of the character stream read from the port.
> If I understand you correctly, that sounds more like "char-ready?".

Erm yes, my mistake.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]