Databases
StackOverflow2013
Postsdbo
POCross browser Javascript number precision
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCross browser Javascript number precision
    primarykey
    data
    text
    <p>Within JavaScript, numbers are defined as 64bit double-precision. I have a specific use in mind for a distributed web application, which would only work if I can rely on consistent results across all browsers.</p> <p>Despite the spec using the IEEE standard, I naturally have a suspicion that there may be tiny differences in implementations of the maths library or even the underlying hardware, which could cause compound errors.</p> <p>Is there any source of compatibility data, or a reliable test suite to verify double precision calculations in the browser? In particular, I also need to consider mobile browsers (usually ARM based).</p> <p>Clarification -</p> <p>This is a question about browser compatibility. I'm trying to understand whether all browsers can be relied upon to treat numbers in a reliable, consistent and repeatable way as defined for IEEE floating point. In most languages this is a safe assumption, but it's interesting that there's a little uncertainty about this in the browser.</p> <p>There's been some great advice on how to avoid floating point problems due to lack of precision and rounding errors. In most cases, if you require accuracy you should follow this advice!</p> <p>For this question, I'm not trying to avoid the problem but understand it. Floating point numbers are inherently inaccurate by design, but as long as some care is taken with how builds are made that inaccuracy can be completely predictable and consistent. IEEE-754 describes this to a level of detail that only a standards body could.</p> <p>I've decided to offer a small bounty if anyone can cite,</p> <ul> <li>Genuine compatibility data relating to the implementation of IEEE numbers in mainstream browsers. </li> <li>A test suite intended to verify the implementation within the browsers, including verifying the correct internal use of a 64 bit floating point number (53 bit mantissa).</li> </ul> <p>In this question I'm not looking for alternative options, workarounds or ways to avoid the problem. Thank you for the suggestions.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USleebriggs
    1. USleebriggs
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POCross browser Javascript number precision
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POCross browser Javascript number precision
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POCross browser Javascript number precision
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI cannot answer your question, but have you considered using Strings instead? Math may be little more difficult, but then you'll never have to worry about precision.
      singulars
      1. POCross browser Javascript number precision
      1. USDanny Kirchmeier
    2. CO@DannyKirchmeier - Math may be a _little_ more difficult?
      singulars
      1. POCross browser Javascript number precision
      1. USnnnnnn
    3. CO@DannyKirchmeier: Using strings (I assume you mean things akin to Java's `BigDecimal`, or C#'s `decimal` type) can be useful for financial calculations, but that doesn't mean you don't have to worry about precision, just that you have *different* worries about precision. They can't (for instance) represent one-third precisely.
      singulars
      1. POCross browser Javascript number precision
      1. UST.J. Crowder
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload