public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/47628] non-compliant C++0x erase methods on STL containers Date: Mon, 07 Feb 2011 09:44:00 -0000 [thread overview] Message-ID: <bug-47628-4-gnU08alveg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47628-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47628 --- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-02-07 09:30:42 UTC --- Oops, I think I'm confusing this with another related issue - despite what I said we do seem to have changed the signature, and we currently implement the C++0x draft spec. Tables 99 and 100 say erase takes a const_iterator, so does the synopsis of each container
next prev parent reply other threads:[~2011-02-07 9:30 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-07 1:00 [Bug libstdc++/47628] New: " blelbach at cct dot lsu.edu 2011-02-07 1:14 ` [Bug libstdc++/47628] " blelbach at cct dot lsu.edu 2011-02-07 9:30 ` redi at gcc dot gnu.org 2011-02-07 9:44 ` redi at gcc dot gnu.org [this message] 2011-02-07 11:26 ` paolo.carlini at oracle dot com 2011-02-07 14:22 ` blelbach at cct dot lsu.edu 2011-02-07 17:18 ` redi at gcc dot gnu.org 2011-02-07 17:23 ` redi at gcc dot gnu.org 2011-02-07 17:56 ` paolo.carlini at oracle dot com 2011-02-07 17:57 ` paolo.carlini at oracle dot com 2011-02-07 18:01 ` paolo.carlini at oracle dot com 2011-02-07 18:05 ` redi at gcc dot gnu.org 2011-02-07 20:19 ` paolo at gcc dot gnu.org 2011-02-07 20:25 ` paolo.carlini at oracle dot com 2011-02-23 14:15 ` redi at gcc dot gnu.org
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=bug-47628-4-gnU08alveg@http.gcc.gnu.org/bugzilla/ \ --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).