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 libstdc++/27404] Rope iterators are not InputIterators Date: Wed, 03 May 2006 00:08:00 -0000 [thread overview] Message-ID: <20060503000830.28516.qmail@sourceware.org> (raw) In-Reply-To: <bug-27404-10727@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from pcarlini at suse dot de 2006-05-03 00:08 ------- Hi Doug. I'm afraid that, everything considered - in particular the status of the rope extension - we have to go with the ugly approach: things like _Rope_iterator::_M_check() actively do change the object... -- pcarlini at suse dot de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2006-05-03 00:08:30 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27404
next prev parent reply other threads:[~2006-05-03 0:08 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-02 21:43 [Bug libstdc++/27404] New: " doug dot gregor at gmail dot com 2006-05-03 0:08 ` pcarlini at suse dot de [this message] 2006-05-04 9:39 ` [Bug libstdc++/27404] " paolo at gcc dot gnu dot org 2006-05-04 9:40 ` 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=20060503000830.28516.qmail@sourceware.org \ --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).