Hi Sean,
> You should also take note of our existing EQUAL(), NEAR_EQUAL(), ZERO(), and
> NEAR_ZERO() macros (as well as vector versions) in include/vmath.h
> To handle floating point fuzz, it may even be necessary to check if values
> are > -TOL, but requires forethought into what the number means.
This function is used to sort the array, so I think strict floating point
comparison is reasonable. The original implementation is wrong because it just
returns the result of minus (implicit conversion to int), which makes two
floating points that differ less than 1 to equal.
Have I misunderstood your comment?
Cheers!
Wu
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
