ObjFW  History of src/OFMatrix4x4.h of b77972796e222c31

Changing the alignment of OFVector4D globally (as was done previously)
would have technically been an ABI break in extremely rare cases.
However, since we only need the alignment for the methods added after
1.0, it's better to only have the alignment there and get back to full
ABI compatibility with 1.0. file: [06311cf4f1] check-in: [1af54eb2c2] user: js, branch: trunk, size: 2967 [annotate] [blame] [check-ins using] [diff]

This should work now that objects are properly aligned. file: [e3aa63e106] check-in: [71237f1a49] user: js, branch: trunk, size: 2727 [annotate] [blame] [check-ins using] [diff]

This requires the vectors to be 16 byte aligned. In order to achieve
this, the OFVector4D type is changed to have an alignment of 16 bytes.
However, this does *not* break ABI because the only method actually
requiring 16 byte alignment is -[transformVectors:count:], which was not
in ObjFW 1.0. Hence binaries compiled for ObjFW 1.0 have no 16 byte
alignment for OFVector4D, but also cannot ever call into any code that
needs it. (-[transformedVector:] calls into -[transformVectors:count:],
but creates a properly aligned copy that it passes.) file: [12afeb3f7a] check-in: [7f304f573b] user: js, branch: trunk, size: 2676 [annotate] [blame] [check-ins using] [diff]

This allows writing matrices more naturally, without having to transpose
them in the source. file: [817b6aa381] check-in: [975a812f36] user: js, branch: trunk, size: 2396 [annotate] [blame] [check-ins using] [diff]

For now, we're only interested in transformed points. file: [32857d56d5] check-in: [db7991d07b] user: js, branch: trunk, size: 2111 [annotate] [blame] [check-ins using] [diff]

These will be useful for 3D graphics. file: [f8bbebd161] check-in: [44eb35b212] user: js, branch: trunk, size: 1898 [annotate] [blame] [check-ins using]