8 Dec
2006
8 Dec
'06
4:46 p.m.
Guillaume Melquiond wrote:
The implementation is generic; you just have to provide a mathematical kernel as a policy (what the documentation calls the "rounding policy") in order to describe how to perform operations on values of type T [2]. That is, once you said how to divide values of type T, you can divide values of type interval<T>.
I hadn't realise that, thanks for the correction!
[1] For comparison, n2137 does not mandate a specific representation; an implementation relying on a midpoint-radius one would still be compliant.
Right, that was what I was getting at really: presumably one could write a specialisation for boost::interval<real_big_type> that used value+radius internally? Regards, John.