Yet another copy constructor question

Code:

---

#pragma once

#include "..\SkinnedMesh\skinnedMesh.h"

class Objects
{
public:
        Objects(SkinnedMesh *_mesh) { mesh = _mesh; }
        ~Objects(void) { }

        void setPos(const D3DXVECTOR3& _pos) { pos = _pos; }
        void setRot(const D3DXVECTOR3& _rot) { rot = _rot; }
        void setScale(const D3DXVECTOR3& _scale) { scale = _scale; }

 

protected:
        SkinnedMesh *mesh;
        D3DXVECTOR3 pos;
        D3DXVECTOR3 rot;
        D3DXVECTOR3 scale;
        D3DXQUATERNION rotQuat;
};


class CCB : public Objects
{
        CCB(const CCB& ccb) : mesh(ccb.mesh)

};

---

Here CCB(const CCB& ccb)：mesh(ccb.mesh) says mesh is not a static member of CCB.
Thanks
Jack

Did you mean:

Code:

---

class CCB : public Objects
{
        CCB(const CCB& ccb) : mesh(ccb.mesh) {}

};

---

Hello Victor,
That was a typo, sorry about that.
But the result is still the same.

[google translated]
Error 1 error C2614: 'the CCB': member initialization illegal: 'mesh' is not the base or member class d: \ visual studio projects \ perfectsim \ perfectsim \ Objects \ Objects.h to 29 1 PerfectSim
Thanks
Jack

Have a look at
http://stackoverflow.com/questions/7...ss-constructor
and some other discussions here:
https://www.google.com/search?source...2614&gs_htsa=1

Great thanks, have that fixed.

Quote:

---

Originally Posted by lucky6969b

Great thanks, have that fixed.

---

You may have fixed the compiler error, but I highly doubt that your copy constructor actually creates copies, meaning a runtime nightmare.

I see many members of "Objects" that aren't being copied when the copy constructor is called. So now you have half or semi copies floating around, and that alone can cause all sorts of runtime issues and problems.

The purpose of the copy constructor is not for your personal use. It is called whenever the compiler decides (and you mostly have very little say in this decision) to make a copy. That can occur at times you don't even expect it to happen. Therefore your copy constructor must create a real copy -- not a half or semi-copy. In other words, if I take that copy and use it instead of the original object, the program must externally behave exactly the same.

Since copying (and assignment operator, which you failed to show) is something intrinsic, you can't write a copy-assignment operator that can have side effects, and the way your code looks, it has plenty of side-effects due to the non-copying of all members.

Regards,

Paul McKenzie