This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/9024: Input fails after call to basic_filebuf<>::pubsetbuf(0, 0)
- From: paolo at gcc dot gnu dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, paolo at gcc dot gnu dot org, peturr02 at ru dot is
- Date: 20 Dec 2002 19:07:05 -0000
- Subject: Re: libstdc++/9024: Input fails after call to basic_filebuf<>::pubsetbuf(0, 0)
- Reply-to: paolo at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, paolo at gcc dot gnu dot org, peturr02 at ru dot is, gcc-gnats at gcc dot gnu dot org
Synopsis: Input fails after call to basic_filebuf<>::pubsetbuf(0, 0)
Responsible-Changed-From-To: unassigned->paolo
Responsible-Changed-By: paolo
Responsible-Changed-When: Fri Dec 20 11:07:04 2002
Responsible-Changed-Why:
Analyzed.
State-Changed-From-To: open->feedback
State-Changed-By: paolo
State-Changed-When: Fri Dec 20 11:07:04 2002
State-Changed-Why:
The current behaviour seems standard conforming: according
to 27.8.1.4,10, _only_ if setbuf(0,0) is called before _any_
I/O has occurred the stream becomes unbuffered, otherwise
the results are implementation defined.
Indeed, if the _second_ pubsetbuf call (that at line 52)
is removed from the testcase, basic_ifstream is usable
without problems as expected.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9024