Robert, sorry to have wasted your time. I have wasted mine too.
> The amount of maintenance work with the Vec class is about as close to
> zero as any but of the OSG gets. Maintenance is an non issue.
It's obvious that there has been done no maintenance. This core functionality
has surprises and inconsistencies that hasn't been addressed because noone
want's to update all those files. Examples:
Vec3f * Vec3f => dot product (ok, sort of..)
Vec3i * Vec3i => component multiply (???)
Vec3s * Vec3s => not available (??)
-Vec3f => negate (ok)
-Vec3i => not avaliable (??)
Vec3d + Vec3f => Vec3d (ok)
Vec3f + Vec3d => Vec3f (??) [c++: float + double => double]
Matrixd * Vec3f => Vec3f (?) [c++: double * float => double]
Vec3f * Matrixd => Vec3f (?)
And the the list goes on.
> Stupid programmers will do stupid stuff.
Spot on.
> I don't think you should be expecting the compiler to know
> automatically change it to double, or for the OSG to by default do
> double maths even though you passed in float.
He passed in both float and doubles, so yes he should expect double result.
Mixed float and double expression are computed as double and should be returned
as such. That is how it works in c++, and also in my proposed update, but
whatever.
> You seem to have missed the lecture about "Minimal and Complete".
Maybe, but you seem to have missed the lecture about "Consistent and
Predictable".
@John Ivar: Hi, nice suprise to see you here!
@Jan: Good answers. Thanks.
@Robert, actually sorry for the fuzz. I'm done now.
Cheers,
Tyge
------------------
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=63702#63702
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
