| Wiki Markup |
|---|
According to the Java Language Specification \[[JLS 05|AA. Java References#JLS 05]\], Section 4.2.3, "Floating-Point Types, Formats, and Values|http://java.sun.com/docs/books/jls/third_edition/html/typesValues.html#4.2.3]\]:": |
NaNis unordered, so the numerical comparison operators<,<=,>, and>=returnfalseif either or both operands areNaN. The equality operator==returnsfalseif either operand isNaN, and the inequality operator!=returnstrueif either operand isNaN.
...
A frequently encountered mistake is the doomed comparison with NaN, typically in expressions. As per its semantics, no value (including NaN itself) can be compared to NaN using common operators. This noncompliant code example demonstrates one of the many violations.
| Code Block | ||
|---|---|---|
| ||
public class NaNComparison {
public static void main(String[] args) {
double x = 0.0;
double result = Math.cos(1/x); // returns NaN if input is infinity
if(result == Double.NaN) { // compare with infinity
System.out.println("Both are equal");
}
}
}
|
Compliant Solution
This compliant solution uses the method Double.isNaN() to check if the expression corresponds to a NaN value.
| Code Block | ||
|---|---|---|
| ||
public class NaNComparison {
public static void main(String[] args) {
double x = 0.0;
double result = Math.cos(1/x); // returns NaN if input is infinity
if(Double.isNaN(result)) {
System.out.println("Both are equal");
}
}
}
|
Risk Assessment
Comparisons with NaN values may lead to unexpected results.
...