This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/7744: streambuf::in_avail() always returns 0 (zero) for cin input stream
- From: ljrittle at gcc dot gnu dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, jfischer110 at attbi dot com, nobody at gcc dot gnu dot org
- Date: 28 Aug 2002 21:47:50 -0000
- Subject: Re: libstdc++/7744: streambuf::in_avail() always returns 0 (zero) for cin input stream
- Reply-to: ljrittle at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, jfischer110 at attbi dot com, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
Synopsis: streambuf::in_avail() always returns 0 (zero) for cin input stream
State-Changed-From-To: open->analyzed
State-Changed-By: ljrittle
State-Changed-When: Wed Aug 28 14:47:49 2002
State-Changed-Why:
Please read sections 27.5.2.2.3 27.5.2.4.3 of ISO-C++-14882.
It is my belief that an implementation shall always be able
to return 0. Your portable application must handle an
implementation that always returns 0. At least one famous
C++ (TC++PLSE) author agrees with my belief. Thus, this
is a QoI issue not a bug (reassigned to change-request
from bug). We agree that the current implementation is
poor. Please feel free to provide a patch that refines
our implementation by submitting a patch.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7744