public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Mads" <mki@maconomy.dk> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: RE: libstdc++/6360: Wrong workaround in char_traits.h - ignore stops on \0xff Date: Thu, 18 Apr 2002 08:26:00 -0000 [thread overview] Message-ID: <20020418152602.25733.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/6360; it has been noted by GNATS. From: "Mads" <mki@maconomy.dk> To: <gcc-gnats@gcc.gnu.org>, <nobody@gcc.gnu.org> Cc: Subject: RE: libstdc++/6360: Wrong workaround in char_traits.h - ignore stops on \0xff Date: Thu, 18 Apr 2002 17:23:33 +0200 This is a multi-part message in MIME format. ------=_NextPart_000_0004_01C1E6FE.6E0DE2D0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit I tried to attach the attached file to the bugreport - but failed. Can it be submitted this way? /Mads > -----Original Message----- > From: gcc-gnats@gcc.gnu.org [mailto:gcc-gnats@gcc.gnu.org] > Sent: Thursday, April 18, 2002 5:06 PM > To: mki@maconomy.dk > Subject: Re: libstdc++/6360: Wrong workaround in > char_traits.h - ignore > stops on \0xff > > > Thank you very much for your problem report. > It has the internal identification `libstdc++/6360'. > The individual assigned to look at your > report is: unassigned. > > >Category: libstdc++ > >Responsible: unassigned > >Synopsis: Wrong workaround in char_traits.h - ignore > stops on \0xff > >Arrival-Date: Thu Apr 18 08:06:00 PDT 2002 > ------=_NextPart_000_0004_01C1E6FE.6E0DE2D0 Content-Type: application/octet-stream; name="IstreamIgnore.cpp" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="IstreamIgnore.cpp" #include <iostream>=0A= #include <sstream>=0A= =0A= using namespace std;=0A= =0A= int main()=0A= {=0A= stringstream ss("abcd" "\xFF" "1234abcd");=0A= =0A= char c;=0A= ss >> c;=0A= cout << "1st char is: " << c << endl;=0A= =0A= cout << "Skipping 8 chars (i.e. until after the digits)..." << endl;=0A= ss.ignore(8);=0A= =0A= cout << "The rest of the stream contains: '" << ss.rdbuf() << '\'' << = endl;=0A= =0A= return 0;=0A= }=0A= ------=_NextPart_000_0004_01C1E6FE.6E0DE2D0--
next reply other threads:[~2002-04-18 15:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-18 8:26 Mads [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-04-22 13:31 bkoz 2002-04-19 12:28 bkoz 2002-04-18 8:06 mki
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20020418152602.25733.qmail@sources.redhat.com \ --to=mki@maconomy.dk \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).