>> Anyhow, it seems worth addressing this gap at the written specification >> level. > What would you suggest? We could add a statement to be explicit that no > special / sentinel values (which includes NaN) are recognized as null.
I like your suggestion Wes. Please consider making that amendment (or similar) in the next specification update. Cheers, Rhys
