|
Boost : |
From: Dan W. (danw_at_[hidden])
Date: 2003-12-12 09:48:08
> It seems you didn't really understand. It doesn't happen with big or
> small integers. It happens with integers in the middle (between 2^23 and
> 2^24). With the current implementation, when a floating-point is an
> integer in the correct target range, you are not sure at all that the
> integer you get after the cast is the same as before.
I think I'm starting to understand... Is it that when you say to the
hardware "add .5" the nearest value to .5 it thinks is 1 ? I think I get it.
Any chance I could look at the code for numeric_cast<> without going
through CVS?
(Maybe I can figure out some assembler trick to, at least, not use a branch.)
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk