From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16955 invoked by alias); 5 Feb 2002 15:26:01 -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 16913 invoked by uid 71); 5 Feb 2002 15:26:00 -0000 Date: Tue, 05 Feb 2002 07:26:00 -0000 Message-ID: <20020205152600.16902.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Carlo Wood Subject: Re: libstdc++/5583: std::set::iterator is readonly Reply-To: Carlo Wood X-SW-Source: 2002-02/txt/msg00113.txt.bz2 List-Id: The following reply was made to PR libstdc++/5583; it has been noted by GNATS. From: Carlo Wood To: rodrigc@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, mathias.hasselmann@gmx.de, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: libstdc++/5583: std::set::iterator is readonly Date: Tue, 5 Feb 2002 16:18:40 +0100 On Tue, Feb 05, 2002 at 02:56:09PM -0000, rodrigc@gcc.gnu.org wrote: > Synopsis: std::set::iterator is readonly > > State-Changed-From-To: open->feedback > State-Changed-By: rodrigc > State-Changed-When: Tue Feb 5 06:56:09 2002 > State-Changed-Why: > Your testcase in the "How-to-Repeat" section is > incorrect and doesn't even compile. > Can you submit a full testcase (including #include statements) > which illustrates your problem? > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5583 I didn't look at the PR, but from the Subject I bet that he means that (*iter) returns a constant object, even for set::iterator. If so, then this is not a bug: the elements of set<> have to be constant, you are not allowed to change them because that would change the ordering in the set<>. -- Carlo Wood