Refactoring Vector2D, Vector3D (a.k.a. Vec2, Vec3, etc) about playrho HOT 2 CLOSED

I believe dropping the field accessors in favor of real array composition will also facilitate use of SSE and other parallel processing capabilities. But if this change is going to happen, it needs to happen IMO before launch so less users had to rewrite their code from using .x and .y to using [0] and [1].

from playrho.

This is done now and passes all builds/tests as of commit aad9ebb.

So no more access to Vec2 or Length2D etc via .x or .y.

If a programmer wants to access elements by horizontal or vertical concepts, the template functions GetX and GetY are there now for that. If a programmer wants to access elements by array concepts, the template functions std::get<0> and std::get<1> are there now for this (and implemented for the base Vector template structure). These are all compile-time safe too in that their setup is such that the compiler should output an error if you were to try and do something like access element 4 via code like std::get<4>. I think these should be the recommended ways to access the Vector based types.

Alternatively, the Vector based types can all be accessed like arrays; with subscripts. Like: location[0] or location[1]. Out-of-bounds access as arrays is not guaranteed to be caught by the compiler however.

from playrho.