Thread: Warnings when using vector of vector

I keep getting weird warnings. I have isolated the problem to the following test-case source file:

Code:

#include <vector>

class testclass
{
	public:
		testclass(const testclass &o); // {};
};

void testfunc()
{
	std::vector <std::vector<testclass> > testobj;
	testobj.push_back(std::vector<testclass>());
}

When compiled with
g++ -W -O2 -c C:\Rotzooi\test.cpp -o obj\test.o
I get the following errors:

Code:

stl_vector.h||In member function 
	`std::vector<_Tp, _Alloc>& std::vector<_Tp, _Alloc>::operator=(const std::vector<_Tp, _Alloc>&) 
	[with _Tp = testclass, _Alloc = std::allocator<testclass>]':|
stl_vector.h|715|warning: '__result' might be used uninitialized in this function|
stl_uninitialized.h|82|warning: '__cur' might be used uninitialized in this function|
stl_uninitialized.h|82|warning: '__cur' might be used uninitialized in this function|
stl_uninitialized.h||In member function 
	`void std::vector<_Tp, _Alloc>::_M_insert_aux
	(__gnu_cxx::__normal_iterator<typename _Alloc::pointer, std::vector<_Tp, _Alloc> >, const _Tp&) 
	[with _Tp = std::vector<testclass, std::allocator<testclass> >, 
	_Alloc = std::allocator<std::vector<testclass, std::allocator<testclass> > >]':|
stl_uninitialized.h|82|warning: '__cur' might be used uninitialized in this function|
stl_uninitialized.h|82|warning: '__cur' might be used uninitialized in this function|
stl_uninitialized.h|82|warning: '__cur' might be used uninitialized in this function|
stl_uninitialized.h|82|warning: '__cur' might be used uninitialized in this function|
stl_uninitialized.h|82|warning: '__cur' might be used uninitialized in this function|
stl_uninitialized.h||In function `void testfunc()':|
stl_uninitialized.h|82|warning: '__cur' might be used uninitialized in this function|

(edited for readability)

I do notice I don't get any warnings when I give the constructors function definition right in the class declaration. Also, no warnings without the optimalisation flag (and obviously not without the -W flag). Is this something to be worried about? And why do I get these warnings? Any way to prevent them?
Thanks in advance. I'm really scratching my head at the moment.

Code:

class testclass
{
	public:
		testclass(const testclass &o); // {};
};

void testfunc()
{
    //Vector of test_class vectors
    std::vector <std::vector<testclass> > main_vector;

    //Vector of test_class objects
    std::vector<testclass> testclass_vector;
                
    //Create test_class object
    testclass test_object;
    
    //Add to test_class vector
    testclass_vector.push_back(test_object);

    //Add test_class vector to vector of test class vectors
    main_vector.push_back(testclass_vector);
}

This should fix it. My guess about the warnings is you did not actually have an instance of the vector you were attempting to add to your main vector. When I use complex containers such as this I will use typedef's to make the code easier to follow. Do you really need this complex container? Perhaps you could simplify your design so that you could also simplify your container. While I have used containers this complex I will say that they are confusing at times and usually unecessary. Another level of abstraction could remove the need for this type of container.

Bubba: that code (after adding a default constructor) still generates the same warnings.
Using a typedef or a wrapper class for std::vector<testclass> probably would be the right thing to do but I'd have to rewrite a bunch of code for that to work in what I'm working on. (also, when I tried it in my test code the typedef still generated the same warnings; a wrapper class also still leaves 3 of the 9 warnings)
For now I'll just turn off optimisation and ignore the warnings if I ever need it back. (I really don't, right now)
Thanks for the help guys!