[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: |
Sat, 30 Mar 2013 19:02:31 -0400 (EDT) |
Mark H Weaver:
> I think I now see a reasonable way to fix this.
> First of all, all interfaces that do something like 'peek' would, when
> returning an EOF, set a 'pending_eof' flag in the port structure...
That's awesome, and it sounds like it'd work well.
Thanks for looking into this.
--- David A. Wheeler
- bug#12216: peek-char incorrectly *CONSUMES* eof, (continued)
- 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, 2013/03/14
- bug#12216: peek-char incorrectly *CONSUMES* eof, Mark H Weaver, 2013/03/30
- bug#12216: peek-char incorrectly *CONSUMES* eof,
David A. Wheeler <=
- bug#12216: peek-char incorrectly *CONSUMES* eof, Mark H Weaver, 2013/03/31