This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/9169: filebuf output fails if codecvt<>::out returns noconv
- 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, ncm at cantrip dot org, nobody at gcc dot gnu dot org, paolo at gcc dot gnu dot org, peturr02 at ru dot is
- Date: 16 Feb 2003 16:10:34 -0000
- Subject: Re: libstdc++/9169: filebuf output fails if codecvt<>::out returns noconv
- 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, ncm at cantrip 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: filebuf output fails if codecvt<>::out returns noconv
Responsible-Changed-From-To: unassigned->paolo
Responsible-Changed-By: paolo
Responsible-Changed-When: Sun Feb 16 16:10:33 2003
Responsible-Changed-Why:
Analyzing.
State-Changed-From-To: open->analyzed
State-Changed-By: paolo
State-Changed-When: Sun Feb 16 16:10:33 2003
State-Changed-Why:
Humm. This behavior started when we implemented the resolution of DR19, upon your ;) libstdc++/9168!
Isn't now expected for a noconv facet (the default do_out)
to _not_ store anything in the destination sequence?
Nathan?
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9169