On Fri, Jun 26, 2015 at 7:33 PM, Michael Marcin
On 6/26/2015 1:30 AM, Emil Dotchevski wrote:
Maybe its use as an interop library to stitch disparate libraries
together is enough value to include it in boost. But in that case I think maybe a smaller addition to the Boost.Geometry library is more appropriate.
I do not think that there is any commonality between Geometry and QVM. Sure, QVM operations can be used with Geometry types but they can also be used with the types of any other library.
What I mean is Boost.Geometry already has adapters for point types among other things. You are providing adapters for matrix vector and quaternion types.
http://www.boost.org/doc/libs/1_58_0/libs/geometry/doc/html/geometry/example...
It seems to me Geometry is about shapes and shape operations and iteration. QVM has nothing to do with shapes or iteration, but it defines a complete set of generic namespace-scope quaternion/matrix/vector operations, which Geometry doesn't. I also think that it shouldn't: if you want to use such operations with Geometry types just use the QVM adaptation machinery -- Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode