From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12250 invoked by alias); 3 Jul 2002 17:26:05 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 12226 invoked by uid 71); 3 Jul 2002 17:26:03 -0000 Date: Wed, 03 Jul 2002 10:26:00 -0000 Message-ID: <20020703172603.12225.qmail@sources.redhat.com> To: paolo@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "B. Kosnik" Subject: Re: libstdc++/7186: DR179 for std::deque::iterator and const_iterator Reply-To: "B. Kosnik" X-SW-Source: 2002-07/txt/msg00117.txt.bz2 List-Id: The following reply was made to PR libstdc++/7186; it has been noted by GNATS. From: "B. Kosnik" To: Paolo Carlini 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