This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: rel_ops issues
- To: bkoz at redhat dot com (Benjamin Kosnik)
- Subject: Re: rel_ops issues
- From: Joe Buck <jbuck at racerx dot synopsys dot com>
- Date: Tue, 3 Apr 2001 17:06:39 -0700 (PDT)
- Cc: Gabriel dot Dos-Reis at cmla dot ens-cachan dot fr (Gabriel Dos Reis), Theodore dot Papadopoulo at sophia dot inria dot fr (Theodore Papadopoulo), libstdc++ at gcc dot gnu dot org
> > I agreed with your patch -- sorry if that wasn't clear.
>
> Gentlemen. (Sorry, couldn't resist.)
> Now that everybody's in agreement, can this approved patch please be
> applied? With a testsuite regression so that it never comes back?
The one line patch I sent, and which has been approved, only fixes
one of the two bugs (2406).
The test case was given in that report. Since it's short, I'll repeat
it. This should compile without error:
--------------------------------
#include <vector>
using std::vector;
struct foo { int a; };
bool operator==(const foo&, const foo&);
bool veq(const vector<foo>& a, const vector<foo>& b) {
return a == b;
}
--------------------------------
For 2405, I have described a patch but have not provided it, since it
would be > 10 lines and I don't have papers. We need a volunteer to
write it. Gaby?
(The patch would provide additional versions of operator!=, etc for
normal_iterator).