Processing Not A Number (NaN)

[SercoSteveB]

What are the contents of Boolean Array Out following execution of the VI?

a) {TRUE, TRUE, TRUE}

b) {FALSE, TRUE, TRUE}

c) {TRUE, FALSE, TRUE}

d) {TRUE, TRUE, FALSE}

[MrStevenUND]

I'm going with B. 

Unfortunately, I'm becoming rusty.  I haven't had Labview in about a year now after changing jobs...

[crossrulz]

B

From Wikipedia:

"A comparison with a NaN always returns an unordered result even when comparing with itself."

In other words, an equals comparison with NaN will always result in a False.

[SercoSteveB]

Answer: B.  Nice one MrStevenUND & crossrulz.

I think crossrulz covered this one.

[ashwinilele]

B

[SUYAM]

Can Any one help me out to find why NaN=NaN giving FALSE

[crossrulz]

Read my comment above.  An equals comparison to NaN, even with another NaN, will always return a FALSE.  This is the IEEE standard.

[AuZn]

Number to fractional string converts NaN to "NaN", and so does the Number to exponential string and Number to engineering string (not a suprise since these two also works on floats).

Number to decimal string also convert NaN to "NaN", though a coersion dot appearred at the input.

Number to hex string and number to oct string convert NaN to "7FFFFFFFFFFFFFFF" and "777777777777777777777" respectively. Not sure why oct string only have 21 7s though.