On Fri, Nov 28, 2008 at 4:48 PM, Torne Wuff
<[EMAIL PROTECTED]> wrote:
> Are you aware of any compliance suite, test vectors, etc we could
> 'borrow' to verify our implementation?
See also the ucbtest package, available from http://www.netlib.org/fp/
___
On Fri, Nov 28, 2008 at 4:48 PM, Torne Wuff
<[EMAIL PROTECTED]> wrote:
> Thanks for hunting down all that information! I'm in agreement: we
> should fix this so that it works for 17 digits.
Cool. I think this should make porting easier (and not just for
Python, either).
> Are you aware of any co
On Thu, Nov 27 08 at 7:27:03PM +, Mark Dickinson wrote:
> Many thanks for your input!
No problem! I don't like hearing folks from Nokia implying that our code
is rubbish :)
> I think IEEE 754 is relevant. :-)
Thanks for hunting down all that information! I'm in agreement: we
should fix this
Update: it looks like IEEE 754-1985 does require that
roundtripping works, at least when the rounding mode
is round-to-nearest. From section 5.6 again:
"""
When rounding to nearest, conversion from binary to decimal and back to
binary shall be the identity as long as the decimal string is carried
Torne,
Many thanks for your input!
> IEEE 754 doesn't include string formatting or parsing as far as I know,
> so I think this is irrelevant to whether we are compliant :)
I think IEEE 754 is relevant. :-)
There's a section 5.6 in the original 1985 standard that's called
something like: "Binar
On Thu, Nov 27 08 at 3:58:43PM +0100, Christian Heimes wrote:
> A while ago I contacted Jukka Laurila from the Nokia developer board
> about IEEE 754 support on S60 phones. The information from Jukka may be
> useful for future reference.
OK, I want to weigh in here, but first I need a lil dis
