This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

c++/3628: "using std::rel_ops" blows up std::vector

>Number:         3628
>Category:       c++
>Synopsis:       "using std::rel_ops" blows up std::vector
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Mon Jul 09 13:56:01 PDT 2001
>Originator:     Richard Kreckel
>Release:        gcc version 3.0 (release)
Debian GNU/Linux (potato)
This bug is related to c++/2405, which has been closed already.
Indeed, the example given there seems to be fixed.  But something
similar can be easily triggered with the GCC-3.0 release by 
this example:
#include <iostream>
#include <vector>
#include <utility>
using namespace std;
using namespace std::rel_ops;

int main(void)
    vector<int> iv;
    for (vector<int>::iterator i=iv.begin(); i!=iv.end(); ++i) { }

Q: Does this qulify as a regression?  After all in gcc-2.95 there was no
such thing as namespace rel_ops and the applications worked fine.



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]