When working with floating point numbers in Java, you may notice that double sometimes produces unexpected or imprecise results. This behavior can lead to errors, especially in financial applications or scenarios that require high accuracy.
In this article, we will delve into the root cause of this problem, explain how to avoid it, provide a working example, and explore whether newer Java versions provide better alternatives.
Why does double lose precision?
1. IEEE 754 floating point standard
The double data type in Java follows the IEEE 754 floating point number operation standard. It represents numbers in binary format using:
- 1 bit is used for symbols,
- 11 bits for exponent,
- 52 bits are used for fractions (mantissa).
This binary representation introduces limitations:
- Limited precision: double can only accurately represent up to 15-17 decimal digits.
- Rounding Error: Many decimal fractions (e.g., 0.1) cannot be represented exactly as binary numbers, resulting in rounding errors.
For example, in binary:
- 0.1 becomes an infinitely recurring decimal that is truncated for storage, thereby introducing slight inaccuracies.
2. Cumulative error in arithmetic operations
Operations involving double may accumulate errors:
- Repeated additions/subtractions amplify rounding errors.
- Multiplication/division may lose precision due to truncation.
This behavior is inherent to floating point arithmetic and is not unique to Java.
Workable example: precision loss caused by using double
Here is an example demonstrating the problem:
public class DoublePrecisionLoss { public static void main(String[] args) { double num1 = 0.1; double num2 = 0.2; double sum = num1 + num2; System.out.println("預(yù)期和:0.3"); System.out.println("實(shí)際和:" + sum); // 比較 if (sum == 0.3) { System.out.println("和等于0.3"); } else { System.out.println("和不等于0.3"); } } }
Output:
<code>預(yù)期和:0.3 實(shí)際和:0.30000000000000004 和不等于0.3</code>
The result 0.30000000000000004 highlights the rounding error caused by the binary representation. Even trivial differences can cause major problems in critical systems.
How to avoid accuracy loss
1. Use BigDecimal for precise calculations
The BigDecimal class in Java provides arbitrary precision arithmetic, making it ideal for scenarios that require high precision (such as financial calculations).
Example using BigDecimal:
import java.math.BigDecimal; public class BigDecimalExample { public static void main(String[] args) { BigDecimal num1 = new BigDecimal("0.1"); BigDecimal num2 = new BigDecimal("0.2"); BigDecimal sum = num1.add(num2); System.out.println("預(yù)期和:0.3"); System.out.println("實(shí)際和:" + sum); // 比較 if (sum.compareTo(new BigDecimal("0.3")) == 0) { System.out.println("和等于0.3"); } else { System.out.println("和不等于0.3"); } } }
Output:
<code>預(yù)期和:0.3 實(shí)際和:0.3 和等于0.3</code>
By using BigDecimal, precision issues are eliminated and comparisons produce correct results.
2. Use Epsilon value for comparison
Another way to deal with loss of precision is to compare floating point numbers with a tolerance (epsilon). This method checks whether the numbers are "close enough" rather than relying on exact equality.
Example using Epsilon comparison:
public class EpsilonComparison { public static void main(String[] args) { double num1 = 0.1; double num2 = 0.2; double sum = num1 + num2; double epsilon = 1e-9; // 定義一個(gè)小的容差值 System.out.println("預(yù)期和:0.3"); System.out.println("實(shí)際和:" + sum); // 使用epsilon進(jìn)行比較 if (Math.abs(sum - 0.3) < epsilon) { System.out.println("和大約等于0.3"); } else { System.out.println("和不等于0.3"); } } }
Output:
public class DoublePrecisionLoss { public static void main(String[] args) { double num1 = 0.1; double num2 = 0.2; double sum = num1 + num2; System.out.println("預(yù)期和:0.3"); System.out.println("實(shí)際和:" + sum); // 比較 if (sum == 0.3) { System.out.println("和等于0.3"); } else { System.out.println("和不等于0.3"); } } }
Why use Epsilon to compare?
- <靈> Flexibility : It allows small differences caused by the incorporation error. <單> Simple
- : This method does not require external libraries and efficiency is high.
Apache Commons Math is a library designed for complex mathematical computing. Although it does not provide arbitrary accuracy arithmetic like Bigdecimal, it provides practical procedures that simplify numerical operations and minimize floating -point errors in some cases.
Example: Use precision.equals to compare
<出> Output:
<code>預(yù)期和:0.3 實(shí)際和:0.30000000000000004 和不等于0.3</code>
Why use Apache Commons math?
import java.math.BigDecimal; public class BigDecimalExample { public static void main(String[] args) { BigDecimal num1 = new BigDecimal("0.1"); BigDecimal num2 = new BigDecimal("0.2"); BigDecimal sum = num1.add(num2); System.out.println("預(yù)期和:0.3"); System.out.println("實(shí)際和:" + sum); // 比較 if (sum.compareTo(new BigDecimal("0.3")) == 0) { System.out.println("和等于0.3"); } else { System.out.println("和不等于0.3"); } } }
Simplified comparison
: Precision.equals allows the use of specified tolerant to compare with the specified tolerance, so as to easily handle the incorporation error.- Lightweight : The library provides tools that focus on numerical calculations without increasing the expenses of BigDecimal.
- Summary Understanding the limitation
Bigdecimal
: Bigdecimal can ensure accuracy, but may affect performance for financial or critical calculations.- Using library : Apache Commons Math provides practical programs such as Precision.equals, which can effectively handle floating -point comparison.
- By understanding Double and its alternatives, you can write more robust and more accurate Java applications. If you encounter the accuracy of Double and how to solve these problems, please tell me in the comments! ?
The above is the detailed content of Why double Loses Precision and How to Avoid It in Java. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

The difference between HashMap and Hashtable is mainly reflected in thread safety, null value support and performance. 1. In terms of thread safety, Hashtable is thread-safe, and its methods are mostly synchronous methods, while HashMap does not perform synchronization processing, which is not thread-safe; 2. In terms of null value support, HashMap allows one null key and multiple null values, while Hashtable does not allow null keys or values, otherwise a NullPointerException will be thrown; 3. In terms of performance, HashMap is more efficient because there is no synchronization mechanism, and Hashtable has a low locking performance for each operation. It is recommended to use ConcurrentHashMap instead.

Java uses wrapper classes because basic data types cannot directly participate in object-oriented operations, and object forms are often required in actual needs; 1. Collection classes can only store objects, such as Lists use automatic boxing to store numerical values; 2. Generics do not support basic types, and packaging classes must be used as type parameters; 3. Packaging classes can represent null values ??to distinguish unset or missing data; 4. Packaging classes provide practical methods such as string conversion to facilitate data parsing and processing, so in scenarios where these characteristics are needed, packaging classes are indispensable.

StaticmethodsininterfaceswereintroducedinJava8toallowutilityfunctionswithintheinterfaceitself.BeforeJava8,suchfunctionsrequiredseparatehelperclasses,leadingtodisorganizedcode.Now,staticmethodsprovidethreekeybenefits:1)theyenableutilitymethodsdirectly

The JIT compiler optimizes code through four methods: method inline, hot spot detection and compilation, type speculation and devirtualization, and redundant operation elimination. 1. Method inline reduces call overhead and inserts frequently called small methods directly into the call; 2. Hot spot detection and high-frequency code execution and centrally optimize it to save resources; 3. Type speculation collects runtime type information to achieve devirtualization calls, improving efficiency; 4. Redundant operations eliminate useless calculations and inspections based on operational data deletion, enhancing performance.

Instance initialization blocks are used in Java to run initialization logic when creating objects, which are executed before the constructor. It is suitable for scenarios where multiple constructors share initialization code, complex field initialization, or anonymous class initialization scenarios. Unlike static initialization blocks, it is executed every time it is instantiated, while static initialization blocks only run once when the class is loaded.

InJava,thefinalkeywordpreventsavariable’svaluefrombeingchangedafterassignment,butitsbehaviordiffersforprimitivesandobjectreferences.Forprimitivevariables,finalmakesthevalueconstant,asinfinalintMAX_SPEED=100;wherereassignmentcausesanerror.Forobjectref

Factory mode is used to encapsulate object creation logic, making the code more flexible, easy to maintain, and loosely coupled. The core answer is: by centrally managing object creation logic, hiding implementation details, and supporting the creation of multiple related objects. The specific description is as follows: the factory mode handes object creation to a special factory class or method for processing, avoiding the use of newClass() directly; it is suitable for scenarios where multiple types of related objects are created, creation logic may change, and implementation details need to be hidden; for example, in the payment processor, Stripe, PayPal and other instances are created through factories; its implementation includes the object returned by the factory class based on input parameters, and all objects realize a common interface; common variants include simple factories, factory methods and abstract factories, which are suitable for different complexities.

There are two types of conversion: implicit and explicit. 1. Implicit conversion occurs automatically, such as converting int to double; 2. Explicit conversion requires manual operation, such as using (int)myDouble. A case where type conversion is required includes processing user input, mathematical operations, or passing different types of values ??between functions. Issues that need to be noted are: turning floating-point numbers into integers will truncate the fractional part, turning large types into small types may lead to data loss, and some languages ??do not allow direct conversion of specific types. A proper understanding of language conversion rules helps avoid errors.
