This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/51841] New: iterator weirdness. I couldn't tell you what's going on here
- From: "marcus-yass at ihug dot co.nz" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 13 Jan 2012 01:05:03 +0000
- Subject: [Bug c++/51841] New: iterator weirdness. I couldn't tell you what's going on here
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51841
Bug #: 51841
Summary: iterator weirdness. I couldn't tell you what's going
on here
Classification: Unclassified
Product: gcc
Version: 4.6.2
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: marcus-yass@ihug.co.nz
Whenever I start using vector::iterators I start running into a variety of
completely unhelpful[probably delusional] compile errors. Attached is a simple,
perfectly reasonable source file that provokes such an error.
compilation: g++-4.6 -std=c++0x 1.cpp
As you can see you get comparable results from using a bare sub-class that has
a similar position as vector::iterators.
In the less trivial source file I got the complaint "porousVect.cpp:67:36:
error: âstd::vector<T, std::allocator<T> >::iteratorâ is not a type".
It so /is/. If you'd like to look at that one too I'll strip it down and post
it for you.