The problem is that an NAN is ... well, not a number. Thus, you can't use it in expressions that require a number. (Think of it as a mathematical Catch-22, if you like.)
The proper way to write this code is like this:
IF(Finite(value) EQ 0 THEN BEGIN Print,'Not a number' ENDIF ELSE BEGIN Print,'Is a number!' ENDELSE
It is then that we all learned even simple answers aren't always so simple. Tom McGlynn immediately responded with this clarification.
That doesn't distinguish NaN from the infinities. The standard trick in any language for looking for NaN's is
if x ne x then begin print,'This is a NaN' endif else ...This can get optimized away if the compiler/interpreter is poorly designed. NaN's are not equal to anything --- even themselves.
To which Ken Bowman, who wisely was keeping his eye on the documentation, replied.
The FINITE function has three keywords: NAN, INFINITY, and SIGN to distinguish between NaNs, Infs, and to return the signs of arguments.
Note that you can only use NaNs in floating point (!Values.F_NaN) and double precision (!Values.D_NaN) arrays. There is no NaN bit pattern for byte, integer, or long data types.