This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/2017
- To: nobody at gcc dot gnu dot org
- Subject: Re: c++/2017
- From: Craig Rodrigues <rodrigc at mediaone dot net>
- Date: 11 Mar 2001 16:46:01 -0000
- Cc: gcc-prs at gcc dot gnu dot org,
- Reply-To: Craig Rodrigues <rodrigc at mediaone dot net>
The following reply was made to PR libstdc++/2017; it has been noted by GNATS.
From: Craig Rodrigues <rodrigc@mediaone.net>
To: Rafael Jesus Alcantara Perez <rafa@dedalo-ing.com>
Cc: Craig Rodrigues <rodrigc@mediaone.net>
Subject: Re: c++/2017
Date: Tue, 20 Feb 2001 12:29:13 -0500
On Tue, Feb 20, 2001 at 10:24:48AM +0100, Rafael Jesus Alcantara Perez wrote:
> Thanks, I have compiled GCC in a GLIBC 2.2 system, and that problem has
> disappeared. Although, I have found another with streams (#2017).
I looked at 2017. I will get a more definitive answer, but
from section 21.6.2 of The C++ Programming Language, 3rd ed. by Stroustrup:
"Unfortunately backing up an input streams is not always possible....
What is guaranteed is that you can back up one character after a successful
read. The peek() reads the next character but leaves
it in the streambuf so that it can be read again."
By the way, I tried your example under C++ compilers from
Sun and Compaq, and they both produced the same result as
gcc 3.0.
--
Craig Rodrigues
http://www.gis.net/~craigr
rodrigc@mediaone.net