This question already has answers here:
What is the intuitive reason that NaN != NaN?
(1 answer)
Why is NaN === NaN false? [duplicate]
(3 answers)
Closed 4 years ago.
NaN==NaN
returns false in javascripts. i want to know some clear explanation.
typeof NaN is number
Number == Number is return true
Then why NaN==NaN is false. Thanks advance.
Related
This question already has answers here:
Why is one string greater than the other when comparing strings in JavaScript?
(5 answers)
Closed 4 years ago.
Can anyone explain me why this:
"Hello" > "World"
is returning false?
It compares them char by char, first it compares "H" > "W" and since that's false. It returns false.
This question already has answers here:
Understanding JavaScript Truthy and Falsy
(9 answers)
Is empty string treated as falsy in javascript?
(5 answers)
Closed 4 years ago.
I have tried 2 conditions in JavaScript and output:
if(""){console.log("Called")} //No Output
if("_"){console.log("Called")} //Output: Called
What could be the possible reason for this?
The empty string is considered as a 'falsy' value, and so it's equivalent to doing:
if(false){console.log("Called")}
The empty string is equal to False if you cast it to Boolean (Type Conversion).
console.log(Boolean("")) //output: false
console.log(Boolean("somestring")) //output: true
This question already has an answer here:
How do the JavaScript relational comparison operators coerce types?
(1 answer)
Closed 8 years ago.
I am wondering if anyone can explain the behavious of comparison operators when using booleans and integers.
Why do the following statements produce the results they do?
false < = 9 // true
false >= 9 // false
Thanks
The representation of false in memory is 0. That's why you obtain those results.
This question already has answers here:
Why is NaN === NaN false? [duplicate]
(3 answers)
Closed 8 years ago.
Can you explain the logical evaluation of NaN in javascript?
NaN==NaN (false)
!NaN==!NaN (true)
NaN!=NaN (true)
NaN==false (false)
NaN==true (false)
I am a little surprised here...
Because that's what the spec says.
Specifically, the IEE floating point spec says that NaN does not equal itself.
Therefore, in Javascript, there is no value that NaN can ever equal.
!NaN is true, because NaN is a falsy value.
This makes all of your examples obvious.
This question already has answers here:
Why is NaN not equal to NaN? [duplicate]
(6 answers)
Closed 9 years ago.
What is the reasoning? I believe this is the only value not equal to itself in JavaScript.
NaN isn't equal to NaN
Use the IsNaN function to check it
See here