GNU bug report logs -
#10627
char-ready? is broken for multibyte encodings
Previous Next
Reported by: Mark H Weaver <mhw <at> netris.org>
Date: Sat, 28 Jan 2012 10:24:02 UTC
Severity: normal
Done: Andy Wingo <wingo <at> pobox.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Hi Mark,
Are you proposing that `char-ready?' do a nonblocking read if
the buffer is empty? That could work.
On Mon 25 Feb 2013 01:06, Mark H Weaver <mhw <at> netris.org> writes:
> However, is seems to me that implementing this in terms of read-byte and
> unget-byte is simpler, because it avoids duplication of the logic
> regarding putback buffers and refilling of buffers.
Could work, if the port is nonblocking to begin with.
> I agree that 'char-ready?' is an antiquated interface, but it is
> nonetheless part of the R5RS (and Guile since approximately forever),
> and it is the only way to do a non-blocking read in portable R5RS. It
> seems to me that we ought to try to implement it as well as we can, no?
Do what you like to do :) But if it were my time, I would simply
document that it checks for a byte and not a character and move on.
Andy
--
http://wingolog.org/
This bug report was last modified 8 years and 340 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.