This is the mail archive of the
libstdc++-prs@sources.redhat.com
mailing list for the libstdc++ project.
Re: libstdc++/86: map & set iterator comparisons are not type-safe
- To: nobody at sourceware dot cygnus dot com
- Subject: Re: libstdc++/86: map & set iterator comparisons are not type-safe
- From: Benjamin Kosnik <bkoz at redhat dot com>
- Date: 7 Sep 2000 17:47:00 -0000
- Cc: libstdc++-prs at sourceware dot cygnus dot com,
- Reply-To: Benjamin Kosnik <bkoz at redhat dot com>
The following reply was made to PR libstdc++/86; it has been noted by GNATS.
From: Benjamin Kosnik <bkoz@redhat.com>
To: bgarcia@laurelnetworks.com
Cc: libstdc++-gnats@sourceware.cygnus.com
Subject: Re: libstdc++/86: map & set iterator comparisons are not type-safe
Date: Thu, 7 Sep 2000 10:37:15 -0700 (PDT)
thanks this is an especially well-formed bug report. i'll check this
stuff in later today.
nice to be working with you. . . .
-benjamin
On 7 Sep 2000 bgarcia@laurelnetworks.com wrote:
>
> The problem is that operator==() and operator!=() are
> defined to take _Rb_tree_base_iterator arguments.
> The fix is to make these functions templates that take
> _Rb_tree_iterator<> arguments instead. This should not
> result in any less efficiency, since in both cases these
> functions are declared inline.
>