This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/12875] Weird behaviour in basic_filebuf::setbuf()
- From: "pcarlini at unitus dot it" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 4 Nov 2003 09:21:36 -0000
- Subject: [Bug libstdc++/12875] Weird behaviour in basic_filebuf::setbuf()
- References: <20031102113858.12875.peturr02@ru.is>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12875
------- Additional Comments From pcarlini at unitus dot it 2003-11-04 09:21 -------
Subject: Re: Weird behaviour in basic_filebuf::setbuf()
Scrive peturr02 at ru dot is <gcc-bugzilla@gcc.gnu.org>:
> The current behaviour is conforming, but that doesn't make it OK. IMHO
> basic_filebuf should never discard data unless a serious error has occured.
I see. I'm not sure however that in the past we always enforced the kind of.
very reasonable, behavior that you rather prefer. I'll look into it: in case,
seems easy to simply prevent setbuf from doing anything after open(), for
instance.
Thanks.