I can only speak for P0037 although P0106 has also been reviewed by SG14. Adding <cmath>-like functions was discussed at our meeting in March. It's also briefly discussed in P0037: https://github.com/johnmcfarla ne/fixed_point/blob/master/doc/p0037r3.md#library-support The proposal is quite tightly scoped. However, that doesn't stop me prototyping surrounding features in the reference implementation [ https://github.com/johnmcfarlane/fixed_point/] - especially if I think they might warrant standardization at a later date. These functions are quite a lot to bite off which is why I only supplied a few wrappers so far. I'm sure it's not easy to get better performance that FPU-supported floating-point variants. However, I am interested in seeing if I can make use of the algorithms in Boost.fixed_point. On Mon, Oct 17, 2016 at 9:31 PM, Michael Marcin <mike.marcin@gmail.com> wrote:
On 10/17/2016 4:10 AM, Paul A. Bristow wrote:
Then you will note with approval that Christopher Kormanyos has implemented all the application C Math functions, which also allows the much of the Boost.Math library to be used without further ado. This is a tremendous advantage if you start with existing floating-point code and want to use it with fixed-point.
Which is awesome!
I hope they also make it into the SG14 proposal.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman /listinfo.cgi/boost