public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "B. Kosnik" <bkoz@nabi.net>
To: paolo@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/7186: DR179 for std::deque::iterator and const_iterator
Date: Wed, 03 Jul 2002 10:26:00 -0000	[thread overview]
Message-ID: <20020703172603.12225.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/7186; it has been noted by GNATS.

From: "B. Kosnik" <bkoz@nabi.net>
To: Paolo Carlini <pcarlini@unitus.it>
Cc: bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
   nobody@gcc.gnu.org, paolo@gcc.gnu.org, pcarlini@unitus.it,
   gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/7186: DR179 for std::deque::iterator and const_iterator
Date: Wed, 3 Jul 2002 10:11:17 -0700

 > >    Is there a survey of existing practice for this issue?
 > >
 > Agreed, I'm going to take care of this, surveying the existing
 > practice of 3 or 4 implementations I have access too.
 
 Great.
 
 > > Can all but the reverse_iterator bits go in now, since that will
 > > have ABI-impacting effects?
 > >
 > Well, as I mentioned in the PR, decoupling the reverse_iterator case 
 > from the "normal" iterator case seems difficult for the special 
 > std::deque::iterator and const_iterator case (it isn't for 
 > __normal_iterator, used by the other standard containers). Again, I
 > will do my best in the next weeks.
 
 Hmm. 
 
 Thanks for looking into this.
 
 -benjamin


             reply	other threads:[~2002-07-03 17:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-03 10:26 B. Kosnik [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-24 23:48 paolo
2002-07-24 23:25 bkoz
2002-07-04 10:06 Benjamin Kosnik
2002-07-03 14:36 Paolo Carlini
2002-07-03  9:36 Paolo Carlini
2002-07-03  9:22 bkoz
2002-07-02 12:16 pcarlini

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=20020703172603.12225.qmail@sources.redhat.com \
    --to=bkoz@nabi.net \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=paolo@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: link
Be 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).