realbasic-nug
[Top] [All Lists]

Re: double to string????

To: REALbasic Network Users Group <realbasic-nug@lists.realsoftware.com>
Subject: Re: double to string????
From: Markus Winter <markus_winter@online.de>
Date: Mon, 30 Jun 2008 21:34:16 +0200
Authentication-results: mx.google.com; spf=neutral (google.com: 74.124.194.228 is neither permitted nor denied by best guess record for domain of realbasic-nug-bounces@lists.realsoftware.com) smtp.mail=realbasic-nug-bounces@lists.realsoftware.com
Delivered-to: listarchive@realsoftware.com
In-reply-to: <0EAFF576-C0FE-4AA4-B566-2C23407637DB@frontiernet.net>
Reply-to: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Sender: realbasic-nug-bounces@lists.realsoftware.com
Thread-index: Acja6EhHhvZLQEbbEd28lgAX8sM2Tg==
Thread-topic: double to string????
User-agent: Microsoft-Entourage/11.4.0.080122
> You have to remember that with a 8 byte floating point number only 53
> bits of the 64 bits hold the digits of the number. 11 bits are needed
> to hold the exponent of the number. Because of this an 8 byte UInt64
> value can return more digits than an 8 byte, double, floating point
> number. However, the floating point exponent can take you out to
> powers of 308 or something like that which gives much larger numbers
> than integer can represent; but, you have a limit of 17 digits in a
> double.

Oh dear God. Double precision with 17 numbers after the decimal point I can
happily live with - but that it is restricted to 17 numbers before the
decimal point is shocking.

And I still don't get how it can simply eat two numbers before the decimal
point.

Thanks

Markus



_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>