Hi, On Fri 17 Aug 2012 03:53, "David A. Wheeler" <dwhee...@dwheeler.com> writes:
> Guile's peek-char has a bug; it incorrectly *consumes* eof instead of > just reporting it. I'm not sure there is a sane way to deal with this. Guile's ports are fundamentally binary, underneath. The backing store is a byte buffer that is decoded and encoded to Scheme characters at need, along with vtable to fill and flush that buffer. You can do strange things like unread characters, switch the encoding, and read them back out in a different encoding. There is no way to represent EOF in that buffer. I have the feeling that for interactive use, if you expect to read a EOF from a port and then continue, you have to not use peek-char. You need to handle your own lookahead buffer. I know it's not a great answer, but I can't think of anything else that makes sense. What do you think? Andy -- http://wingolog.org/
