[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#12216: peek-char incorrectly *CONSUMES* eof
From: |
David A. Wheeler |
Subject: |
bug#12216: peek-char incorrectly *CONSUMES* eof |
Date: |
Thu, 14 Mar 2013 13:43:01 -0400 (EDT) |
On Thu, 14 Mar 2013 13:13:39 -0400, Mark H Weaver <address@hidden> wrote:
> One extra check per read primitive is hardly enough of a cost to
> consider abandoning correctness, IMO.
Though I've not reviewed this code, I *think* you'd only need to check when the
buffer is empty. When the buffer is empty, it'll take a while for the OS to
fill it anyway, far more than checking a boolean value.
--- David A. Wheeler
- bug#12216: peek-char incorrectly *CONSUMES* eof, (continued)
- bug#12216: peek-char incorrectly *CONSUMES* eof, Andy Wingo, 2013/03/07
- bug#12216: peek-char incorrectly *CONSUMES* eof, Daniel Hartwig, 2013/03/08
- bug#12216: peek-char incorrectly *CONSUMES* eof, David A. Wheeler, 2013/03/09
- bug#12216: peek-char incorrectly *CONSUMES* eof, Daniel Hartwig, 2013/03/09
- bug#12216: peek-char incorrectly *CONSUMES* eof, Andy Wingo, 2013/03/13
- bug#12216: peek-char incorrectly *CONSUMES* eof, David A. Wheeler, 2013/03/13
- bug#12216: peek-char incorrectly *CONSUMES* eof, Andy Wingo, 2013/03/13
- bug#12216: peek-char incorrectly *CONSUMES* eof, Mark H Weaver, 2013/03/13
- bug#12216: peek-char incorrectly *CONSUMES* eof, Andy Wingo, 2013/03/13
- bug#12216: peek-char incorrectly *CONSUMES* eof, Mark H Weaver, 2013/03/14
- bug#12216: peek-char incorrectly *CONSUMES* eof,
David A. Wheeler <=
- bug#12216: peek-char incorrectly *CONSUMES* eof, Mark H Weaver, 2013/03/30
- bug#12216: peek-char incorrectly *CONSUMES* eof, David A. Wheeler, 2013/03/30
- bug#12216: peek-char incorrectly *CONSUMES* eof, Mark H Weaver, 2013/03/31