public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pcarlini at suse dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/14039] bug in std::find Date: Fri, 06 Feb 2004 10:07:00 -0000 [thread overview] Message-ID: <20040206100659.31138.qmail@sources.redhat.com> (raw) In-Reply-To: <20040206045704.14039.jsiek@osl.iu.edu> ------- Additional Comments From pcarlini at suse dot de 2004-02-06 10:06 ------- ... also, consider DR 244 (NAD): the implementation discussed is identical to ours, and nobody apparently objected to the correctness of *begin != x1 there... I'm really unsure that we really want to "fix" this barring a clarification in the standard. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14039
next prev parent reply other threads:[~2004-02-06 10:07 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-02-06 4:57 [Bug c++/14039] New: " jsiek at osl dot iu dot edu 2004-02-06 9:22 ` [Bug c++/14039] " pcarlini at suse dot de 2004-02-06 9:57 ` pcarlini at suse dot de 2004-02-06 10:07 ` pcarlini at suse dot de [this message] 2004-02-06 14:23 ` [Bug libstdc++/14039] " pcarlini at suse dot de
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=20040206100659.31138.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).