From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12420 invoked by alias); 28 Aug 2002 21:47:50 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 12401 invoked by uid 61); 28 Aug 2002 21:47:50 -0000 Date: Wed, 28 Aug 2002 17:26:00 -0000 Message-ID: <20020828214750.12400.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jfischer110@attbi.com, nobody@gcc.gnu.org From: ljrittle@gcc.gnu.org Reply-To: ljrittle@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jfischer110@attbi.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/7744: streambuf::in_avail() always returns 0 (zero) for cin input stream X-SW-Source: 2002-08/txt/msg00596.txt.bz2 List-Id: 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