That wasn't so bad, having done the right preparations

I've implemented it now for my engine::scene class (IO), all working fine, and no problems anymore with the default assignment/ copy operator. Even following the rule of three, DIY destructor not needed anymore.

A few conclusions/ thaughts:

- I assume there's nothing to do with a vector in my constructor (not setting to NULL or so)

- vector.reserve function is useless when I simply use vector.resize, because in my/ this case I know the exact number/ size

(if I append an object later on, I'll just use 'push back' and it will reserve space for me anyway)

- no forward declarations possible anymore in my header files of the class, because the vector types are no longer pointers

(more includes needed in header file)

- for loops get less readable when using vector.size, returns a vector<int>::size_type instead of regular int

example: for(vector<int>::size_type mi=0;mi<mMeshInstances.size();++mi)

I might consider to use iterators later on, but for now this works fine (no signed/unsigned warnings)

Struggle; when going through my scene file the 1st time and count the needed sizes for lights, meshes, etc etc., I have to save these numbers. So basically I'm using both my member variabel int's to find number of meshes, lights etc.. But afterwards I can use vector.size() to go through all objects. Not sure how I can eliminate having the int's as member vars having the same value as the vector's.size(). Unless I change my allocate memory function with a huge number of input parameters).

Any input is appreciated as always.

Thanks, I'll definately go for the 'auto' keyword.

Regarding the counters, I see 2 options when I keep them local scope:

1. pass all of them through to as function parameters to my AllocateMemory member function (which does the resizes)

2. do the 'resizes' within the function where I go through the file

(3. create a simple struct to save all counters and pass the struct through to the allocatememory function)

I like the idea of having separate functions for separate clear goals, like 'AllocateMemory'.

Not such a biggy, I'll choose one of the options and go on creating nice new stuff

Ps; just finished all changes for the d3dscene class also, worked out quite well.

With one minor bump, I had to change a header in the 'vector' (header) file, because aligned input was not alowed in the 'resize' function:

	void resize(size_type _Newsize, const _Ty &_Val)
//	void resize(size_type _Newsize, _Ty _Val)

i am always amazed at how ppl manage to make very simple things incredibly messy.

What of course is not my intention. What would be the better/ easier solution on this?

anything that doesn't involve hacking into the standard library making it impossible for anybody else to compile your stuff? Or calling constructors and destructors manually?

PPL write graphics engines with C++ all around the world without need to brake the language this way.. it's just the wrong approach to things. I would never want somebody with that attitude in my team.

Just fix your code and get on with it.