I have kinda found the problem. My program is larger than I have let known. I
hadn't. I did isolate them and it did work. I am now trying to add those
other vectors. Thanks alot for the response and it is nice to know that my
copy constructor is not the problem. There was a question there even if the
program was working. By the way I already have the operator= function but I
haven't seen it called yet. Thanks again.
On Tue, 18 Mar 2008 12:19:05 -0700, Al <Al@discussions.microsoft.com>
wrote:
I have just recently change some code to use std::vector instead of CArray.
It saves the data and displays the data after the file is opened again. The
problem starts when I try to add another object to the vector array. First I
load the data from the document to a ListCtrl on a form, where I can add
elements to the vector. I also use the vector to get a pointer to each of the
objects in the vector and add it to each of the ListCtrl items through
SetIttemData(). After items are added to the list control and the submit
button is press, the code goes through the list and if it has a valid
pointer, it will copy over the data at the location. If it has a NULL for a
pointer, I use push_back to enter a newly created object to the vector. This
is where it does not work. I put a break point in the copy construtor and
found by stepping through the code, once I use push_back, the copy
constructor is called more times than the once. In fact it looks like it is
copying the vector all over again and some. Here is my copy constructor in
case it is the problem.
If the vector is not large enough to contain the new items, adding the
items causes it to be reallocated, which invalidates all iterators,
references, and pointers to items in the vector. In effect, it copies the
whole vector to new storage. To control reallocation, use vector::reserve.
For example, there will be no reallocation in the following, just the
initial allocation:
vector<int> v;
v.reserve(10);
for (int i = 0; i < 10; ++i)
v.push_back(i);
While reallocation has the invalidation issue, it's still efficient,
because vector grows its capacity exponentially, e.g. by a factor of 2.
//////////////////////////////////////////////////////////////////////////////////////
// copy constructor
CLeagueEstab::CLeagueEstab(const CLeagueEstab& cpy)
{
m_Address = cpy.m_Address; // CString
m_City = cpy.m_City; // CString
m_Name = cpy.m_Name; // CString
m_Phone = cpy.m_Phone; // CString
m_State = cpy.m_State; // int
m_Zipcode = cpy.m_Zipcode; // CString
} // copy constructor
any ideas?
That copy constructor default constructs all the members and then assigns
them new values. Use the member initialization list to copy construct the
members, e.g.
CLeagueEstab::CLeagueEstab(const CLeagueEstab& cpy)
: m_Address(cpy.m_Address),
...
{
// Empty
}
That said, the compiler will generate a suitable copy ctor for you in this
case, and you don't need to write a copy ctor at all. I would still add a
comment to the class, e.g.
// Default copy ctor suffices.
Of course, you should also think about the assignment operator and
destructor if you're thinking about copy ctors, and their defaults will
also be OK for this class. Again, I'd add a comment to that effect.
--
Doug Harrison
Visual C++ MVP