Thorsten Ottosen wrote:
John Maddock gave two examples: one where we accapted wrong values and one where we rejected correct values. I found the latter somewhat better (because the invariant of bounded_float would be preserved), and if we are able to get that behavior consistently, I would be quite happy.
So maybe most of our problems will be fixed by using >= and <= instead of < and >?
-Thorsten _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Is the following true: if x and y satisfy x <= y (or x >= y) then they will still do so after any truncation from 80 to 64 bits? Then, as Thorsten suggests, <= and >= will never erroneously accept any value. We could then maybe implement < and > using <=, >= and the std::nextafter function, and achieve the same guarantee there. --Johan Råde