This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/29035] Initialisation of std::ostringstream does not work correctly
- From: "pcarlini at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 12 Sep 2006 16:55:41 -0000
- Subject: [Bug libstdc++/29035] Initialisation of std::ostringstream does not work correctly
- References: <bug-29035-13234@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #7 from pcarlini at suse dot de 2006-09-12 16:55 -------
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> >
> > Shouldn't the output be:
> >
> > 6
> > azerty123
> > 9
>
> In case, that would be a separate issue, we never considered implementing that
> behavior. It would be easy, of course. I don't have the standard at hand, are
> you sure about that? (I will check)
I'm checking right now (I'm far from home, not able to work comfortably):
frankly, I cannot find anything in the standard mandating the alternate
behavior. For an ostringstream not opened in app-mode, of course. I find this
behavior consistent with file streams, by the way...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29035