Okay, when an onject is in a std::vector, what does it require for copying? Copy constructor, assignment operator(operator=), or both? And if you have a copy constructor, does the compiler generate the assignment operator automgically?

Default constructable: check
Assignable: sorta-check

The class in question (CPlayer) is inherited from another class (CObject, an almost-ABC). Now, I figured out to write the copy constructor for CPlayer, but operator= is a bit of a problem, due to the inheritance and all. Which does std::vector use (copy ctor or operator=)? Or is that one of those annoying unspecified and implementation dependent things?

Okay, this helping to clear up alot. Thanks. Which brings me to my final question: How can I implement operator= when the class I'm trying to copy inherits from another class? I need the data in the parent, but I don't want to have to paste the same code into the assignment operator for each derived class (When the parent is called CObject, you can tell there is going to be ALOT of derived classes) Is there an easy way to do it, or am I stuck with ctrl-c & ctrl-v?

P.S. Should std::vector:: push_back() cause either to be called? I'd imagine if it had to resize the array, but otherwise?

EDIT: Stupid smileys

[edited by - ze_jackal on October 22, 2002 8:11:00 PM]

derived class function body:

CPlayer CPlayer::operator=(const CPlayer &rhs)
{
CObject::operator=(rhs);
}

... I think you can do that. It should call the CObject's = operator using "this" to let that function do the work.


To find out first-hand when the copy ctor/ operator='s are being called, just put some kind of print-out line inside the copy ctor and op=.

I seem to remember there are a varying number of copy ctor calls (and no op=) each time you push_back a class into a vector (this is why I use a vector of object * when I need speed).

If you use pointers to objects, you won't need either copy ctor or op=, since just the pointer value is messed with.




Notice that sometimes there are only 2 calls (one in the push_back like, and one when the vector copies the data into it's storage space), and sometimes it resizes the vector's space, resulting in more copy ctors firing.

(had to edit this to fix a problem with HTML on the page)


[edited by - Nypyren on October 22, 2002 11:03:27 PM]

Thanks so much for your help, I finally got everything working. Turns out the compiler could generate usable assignment operators, but I might as well hardcode ''em now that I know how to do it.

quote:
CPlayer CPlayer::operator=(const CPlayer &rhs)
{
CObject::operator=(rhs);
}

That is going into my ''Cool shit I never would have thought was possible'' file. That could come in handy.

quote:
To find out first-hand when the copy ctor/ operator=''s are being called, just put some kind of print-out line inside the copy ctor and op=.

I take the time to build a class to output debug info to a log from anywhere, and litter my code with debug prints at the first sign of a bug, and I STILL DIDN''T THINK TO DO THAT! Sometimes the easiest way to find the solution is right under your nose. I guess that''s what the forums are for.