public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: pme@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, wjlcarrot@aol.com Subject: Re: libstdc++/10498: fstream Date: Fri, 25 Apr 2003 18:15:00 -0000 [thread overview] Message-ID: <20030425181521.30775.qmail@sources.redhat.com> (raw) Synopsis: fstream State-Changed-From-To: open->closed State-Changed-By: pme State-Changed-When: Fri Apr 25 18:15:20 2003 State-Changed-Why: First, this is a duplicate (with even less information) of 10485, which was closed with an explanation of the bug in your code. Second, this is not a useful bug report in any case. Please see http://gcc.gnu.org/bugs.html for what we need in a bug report. If, after consulting a C++ textbook or reference on operator>> in IOStreams, you still feel this is a library bug, you need to provide a reproducible testcase. (You can submit it to this bug number instead of starting a new one, and if it's an actual bug, we'll reopen this one.) http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10498
next reply other threads:[~2003-04-25 18:15 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-25 18:15 pme [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-25 13:56 wjlcarrot
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=20030425181521.30775.qmail@sources.redhat.com \ --to=pme@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=wjlcarrot@aol.com \ /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).