On 8/17/12, David A. Wheeler <dwhee...@dwheeler.com> wrote: > FYI, The peek-char functions reports what the next value will be from > read-char, without consuming it... UNLESS it's eof and you're using guile > 1.8. In guile 1.8, the eof is *consumed* by peek-char (as if it were > read-char) instead of just peeking it, so you have to send eof multiple > times in some cases, one for every peek-char. > > This doesn't matter for files (they just keep sending eof), but it makes > interactive use with neoteric-guile odd; control-D doesn't simply exit like > you'd expect. > > I think this is a bug in guile, but once you know what it's doing, I think > it'll be easy to work around (especially for "normal" cases). I plan to > tweak the code to deal with it, now that I know what's going on.
This behavior seems to exist even in 2.0 and 1.6. Given such a long-running bug, it's likely that this is *by design*, not considered a bug. Sincerely, AmkG ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Readable-discuss mailing list Readable-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/readable-discuss
