Tim Peters added the comment: Again, without replacing float input routines too, this is /not/ good enough to ensure eval(repr(x)) == x even across just 100%-conforming 754 platforms.
It is good enough to ensure (well, assuming the code is 100% correct) eval(repr(x)) == x across conforming 754 platforms that go /beyond/ the standard by also supplying correctly rounding input routines. Some platform C libraries do, some don't. For example, I believe glibc does (and builds its I/O code on David Gay's, mentioned before), but that Microsoft's does not (but that Microsoft's do meet the 754 standard, which-- again --isn't strong enough for "shortest output" to round-trip correctly in all cases). __________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue1580> __________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
