Fair enough on the optimisation. I was just guessing about that, and I didn't know the compiler was that smart.

Anyway, for neatness sake. Can we have a set function.

I have bunches of lines like this in my code right now:

Code: Select all

```
mRectangleData.mVertices[ver_index++] = Ogre::Vector3(left, bottom, depth);
mRectangleData.mVertices[ver_index++] = Ogre::Vector3(right, bottom, depth);
mRectangleData.mVertices[ver_index++] = Ogre::Vector3(left, top, depth);
mRectangleData.mVertices[ver_index++] = Ogre::Vector3(right, bottom, depth);
mRectangleData.mVertices[ver_index++] = Ogre::Vector3(right, top, depth);
mRectangleData.mVertices[ver_index++] = Ogre::Vector3(left, top, depth);
```

To me it looks ugly and a little bit confusing if you don't know how a vector and an Vector3 works. PhysX, Opcode and NxOgre all have set function in their vector classes. Honestly I don't know what the big deal is adding a three/four line function to each of the Vector/Quaternion classes.