Tim Peters <t...@python.org> added the comment:
Mark, ya, MS's Visual Studio's ldexp() has, far as I know, always worked this
way. The code I showed was run under the 2019 edition, which we use to build
the Windows CPython.
Raymond,
x = float(i)
is screamingly obvious at first glance.
x = i/1
looks like a coding error at first. The "reason" for different spellings in
different branches looked obvious in the original: one branch needs to divide,
and the other doesn't. So the original code was materially clearer to me.
Both, not sure it helps, but this use of round-to-odd appears akin to the
decimal module's ROUND_05UP, which rounds an operation result in such a way
that, if it's rounded again - under any rounding mode - to a narrower
precision, you get the same narrower result as if you had used that rounding
mode on the original operation to that narrower precision to begin with.
Decimal only needs to adjust the value of the last retained digit to,
effectively, "encode" all possibilities, but binary needs two trailing bits.
"Round" and "sticky" are great names for them :-)
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue45876>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
